The following bug has been logged online:
Bug reference: 4205
Logged by: Bomken Basar
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.0
Operating system: windows xp
Description:Unable to restore database
Details:
I tried to upgrade to postgres 8.2.7 from 8.0
"Tomasz Rybak" <[EMAIL PROTECTED]> writes:
> I tried to use COPY to import 27M rows to table:
> CREATE TABLE sputnik.ccc24 (
> station CHARACTER(4) NOT NULL REFERENCES sputnik.station24 (id),
> moment INTEGER NOT NULL,
> flags INTEGER NOT NULL
> ) INHERITS (sputnik.sputnik);
Joe Conway <[EMAIL PROTECTED]> writes:
> Tom Lane wrote:
>> Yeah, the dblink code should probably try a bit harder to propagate the
>> original error fields.
> Sounds reasonable. Do you think this is a bug fix or an 8.4 enhancement?
8.4 enhancement I think, since a behavioral change here could p
Tom Lane wrote:
"Henry Combrinck" <[EMAIL PROTECTED]> writes:
Description:perform dblink() in begin/exception returns wrong
SQLSTATE code
The code returned is always 42601 (syntax_error) irrespective of the actual
error (eg, unique_violation).
Yeah, the dblink code should probably t
The following bug has been logged online:
Bug reference: 4204
Logged by: Tomasz Rybak
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.3.1
Operating system: Debian Linux
Description:COPY to table with FK has memory leak
Details:
I tried to use COPY to import 2
