The following bug has been logged online:
Bug reference: 2830
Logged by:
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.2.0, older
Operating system: Ubuntu 6.10 2.6.17-10-386, libc6 2.4-1ubuntu12
Description:Wrong results for prepared statements while cluster
Hi,
I'm using PostgreSQL 8.1.4
The problem is very simple to reproduce:
create table test1 (
pk1 text not null,
df1 text,
primary key(pk1)
);
create table test2 (
pk1 text not null,
pk2 text not null,
df2 text,
primary key(pk1,pk2)
);
alter table test2 add constraint c1 foreign
The following bug has been logged online:
Bug reference: 2829
Logged by: Sean
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.2
Operating system: W2K Server
Description:Runaway logs - "SSL SYSCALL error"
Details:
A couple of times in the last month or two (fi
Patrice Beliveau <[EMAIL PROTECTED]> writes:
> The problem is very simple to reproduce:
[ shrug... ] Your trigger suppressed the cascaded deletes. What were
you expecting to happen?
regards, tom lane
---(end of broadcast)-
"" <[EMAIL PROTECTED]> writes:
> Prepared SELECT/UPDATE/DELETE statements produce wrong results if executed
> while target table is being clustered.
The short answer is "don't CLUSTER while the table is in live use" ...
CLUSTER re-inserts all the rows in the table into a fresh table. This
means
"Sean" <[EMAIL PROTECTED]> writes:
> The pg log files are the culprit - they fill up at a rate of about 50 megs a
> minute with lines reading
> "SSL SYSCALL error: A blocking operation was interrupted by a call to
> WSACancelBlockingCall."
We've seen this reported before...
> Is this a psql probl
