The following bug has been logged online:
Bug reference: 6001
Logged by: Marek Nos
Email address: marek@centrum.cz
PostgreSQL version: 9.0
Operating system: Windows 7
Description:date_trunc is not timezone aware
Details:
and other like extract() as well
SELECT
On Sun, May 01, 2011 at 06:48:57PM +, Marek Nos wrote:
>
> The following bug has been logged online:
>
> Bug reference: 6001
> Logged by: Marek Nos
> Email address: marek@centrum.cz
> PostgreSQL version: 9.0
> Operating system: Windows 7
> Description:date_trunc
Hello
one czech user reported a bug in documentation -
http://www.postgresql.org/docs/8.4/static/plpgsql-trigger.html
NEW
Data type RECORD; variable holding the new database row for
INSERT/UPDATE operations in row-level triggers. This variable is NULL
in statement-level triggers and for DELE
2011/4/29 Philippe Reyes Courrau :
>
> The following bug has been logged online:
>
> Bug reference: 6000
> Logged by: Philippe Reyes Courrau
> Email address: philippecour...@gmail.com
> PostgreSQL version: postgresql-9.0.
> Operating system: windows xp sp3
> Description:
Greg Stark writes:
> So is it ok for inserting one row to cause my table to grow by 90GB?
> Or should there be some maximum size increment at which it stops
> growing? What should that maximum be? What if I'm on a big raid system
> where that size doesn't even add a block to every stripe element?
The following bug has been logged online:
Bug reference: 6002
Logged by: Savita
Email address: savita.ha...@gmail.com
PostgreSQL version: 8.3.5
Operating system: AIX
Description:French character show garbled
Details:
Hi
We are facing a problem while inserting a Lat
