Alvaro Herrera <[EMAIL PROTECTED]> writes:
> Should this be backpatched if changed in 8.3?
I'd vote no; it's pretty hard to argue that it's a bug fix
as opposed to a cosmetic improvement.
regards, tom lane
---(end of broadcast)-
Tom Lane wrote:
> "Jim Nasby" <[EMAIL PROTECTED]> writes:
> > This is on a 8.2.3 database; vacuums started by autovacuum don't get
> > their query_start time set.
>
> Hmm. Query_start is actually defined as "time of last client command
> receipt", so it's null just like client_addr/port are. N
"Jim Nasby" <[EMAIL PROTECTED]> writes:
> This is on a 8.2.3 database; vacuums started by autovacuum don't get
> their query_start time set.
Hmm. Query_start is actually defined as "time of last client command
receipt", so it's null just like client_addr/port are. Not sure if
there's anything
This is on a 8.2.3 database; vacuums started by autovacuum don't get
their query_start time set.
select * from pg_stat_activity where current_query like 'VACUUM%';
-[ RECORD 1 ]-+-
datid | 16384
datname | emma2
procpid | 8674
usesy
Volodymyr Kostyrko wrote:
Zdenek Kotala wrote:
I tested on Solaris AMD64 and Sparc v240 (64bit) and it works for me.
Do you use 32bit or 64bit version of postgreSQL and what you have in
.pgpass?
I use sparc64 and my .pgpass file was like:
localhost:5432:*:pgsql:password
Actually i have alrea
Zdenek Kotala wrote:
I tested on Solaris AMD64 and Sparc v240 (64bit) and it works for me. Do
you use 32bit or 64bit version of postgreSQL and what you have in .pgpass?
I use sparc64 and my .pgpass file was like:
localhost:5432:*:pgsql:password
Actually i have already found the cause. Authoriz
I tested on Solaris AMD64 and Sparc v240 (64bit) and it works for me. Do
you use 32bit or 64bit version of postgreSQL and what you have in .pgpass?
Zdenek
Volodymyr Kostyrko wrote:
It seems to me that auth on the local interface(?) is broken somehow on
sparc64.
[data/pg_hba.c
