Re: [BUGS] COPY in readonly transaction.

2005-10-03 Thread Tom Lane
"Alon Goldshuv" <[EMAIL PROTECTED]> writes: > In the folllowing check (copy.c:DoCopy() ), I *think* that the check for the > is_from flag is mistakenly negated. Yeah, it's definitely backward :-( Will fix. regards, tom lane ---(end of broadcast)--

[BUGS] Race condition in dropdb;createdb

2005-10-03 Thread Jim C. Nasby
[EMAIL PROTECTED]:32]~:1%createdb test; CREATE DATABASE [EMAIL PROTECTED]:32]~:2%dropdb test; createdb test; DROP DATABASE createdb: database creation failed: ERROR: source database "template1" is being accessed by other users [EMAIL PROTECTED]:32]~:3% I realize that the changes made in 8.1 WRT u

[BUGS] COPY in readonly transaction.

2005-10-03 Thread Alon Goldshuv
In the folllowing check (copy.c:DoCopy() ), I *think* that the check for the is_from flag is mistakenly negated. is_from means -> from file to database, therefore we should check for , and not . The current code allows loading and disallows reading in read-only. /* check read-only transaction

Re: [BUGS] Unreliable pg_stat_activity, Windows 2000, PostgreSQL 8.1 beta2

2005-10-03 Thread Jean-Pierre Pelletier
We were running 7.4 under Cygwin with Windows 2000 Service Pack 4. - Original Message - From: "Jim C. Nasby" <[EMAIL PROTECTED]> To: "Jean-Pierre Pelletier" <[EMAIL PROTECTED]> Cc: Sent: Monday, October 03, 2005 6:00 PM Subject: Re: [BUGS] Unreliable pg_stat_activity, Windows 2000, Pos

Re: [BUGS] Unreliable pg_stat_activity, Windows 2000, PostgreSQL 8.1 beta2

2005-10-03 Thread Jim C. Nasby
How were you running 7.4? Under cygwin or on a different OS? On Mon, Oct 03, 2005 at 12:21:09PM -0400, Jean-Pierre Pelletier wrote: > Hi, > > pg_stat_activity sometimes list no connections or a number of connections > much smaller than the number of postgres.exe processes. > > We also have these

[BUGS] Unreliable pg_stat_activity, Windows 2000, PostgreSQL 8.1 beta2

2005-10-03 Thread Jean-Pierre Pelletier
Hi, pg_stat_activity sometimes list no connections or a number of connections much smaller than the number of postgres.exe processes. We also have these messages in our PostgreSQL log approximately 20 times a day. FATAL: could not read from statistics collector pipe: No error FATAL: could not