Not sure if this is a bug or by design in 8.1.2. Using the
following:
log_connections = on
log_disconnections = on
log_duration = on
log_statement = 'all'
log_line_prefix = '%m [%p] %u %r %d %x '
...the transaction is not printed with the duration (it prints 0
instead).
Ed
--
"Ed L." <[EMAIL PROTECTED]> writes:
> ...the transaction is not printed with the duration (it prints 0
> instead).
It's already out of the transaction by the time it prints the duration,
if you're talking about a command that's not within an explicit BEGIN
block. I think this is correct --- to d
The following bug has been logged online:
Bug reference: 2366
Logged by: Christian Holtje
Email address: [EMAIL PROTECTED]
PostgreSQL version: 7.4.8
Operating system: Ubuntu 5.10
Description:Timestamptz data type is inaccurate
Details:
I don't know what's going on,
The following bug has been logged online:
Bug reference: 2365
Logged by: Bujic Nikola
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.1
Operating system: windows xp
Description:can't install
Details:
I getting mesage that postgres account already exists, but
Christian Holtje wrote:
> I don't know what's going on, but basically, for some dates timestamptz is
> loosing parts of the date/time (like the timezone, etc.)
>
> db=# select '2076-03-30 19:57:05-05'::timestamptz;
> timestamptz
> -
> 2076-03-31 00:57:05
> (1 row)
Times
"Christian Holtje" <[EMAIL PROTECTED]> writes:
> I don't know what's going on, but basically, for some dates timestamptz is
> loosing parts of the date/time (like the timezone, etc.)
> db=# select '2076-03-30 19:57:05-05'::timestamptz;
> timestamptz
> -
> 2076-03-31 00:57
