[EMAIL PROTECTED] wrote:
this is a global database problem and pg_dump does not help
how can i fix the database
I don't know how your table got into that state, but since there's only
17 duplicate rows, you could pg_dump, remove the duplicate rows by hand
from the dump-file, and restore.
The following bug has been logged online:
Bug reference: 2796
Logged by: yyang
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.1.3
Operating system: windows 2000
Description:Command: Listen and Notify
Details:
Postmaster server is started successfully.
We can
The following bug has been logged online:
Bug reference: 2801
Logged by: carmelo
Email address: [EMAIL PROTECTED]
PostgreSQL version: 7.4.7
Operating system: debian linux
Description:zope 2.5.1-2.6 doesn't work with postgresql 7.4.7
Details:
When I try to connect my
The following bug has been logged online:
Bug reference: 2797
Logged by: yyang
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.1.3
Operating system: windows 2000
Description:Command: Listen and Notify
Details:
Postmaster server is started successfully.
I can
The following bug has been logged online:
Bug reference: 2798
Logged by: Daniel Baldoni
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.2rc
Operating system: Any
Description:Obsolete tiemzone data included
Details:
G'day folks,
This may not qualify as a "bug
The following bug has been logged online:
Bug reference: 2799
Logged by: Dzmitry Lazerka
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.2rc1
Operating system: WinXP SP2
Description:MSI fatal error when changing. errcode 2864
Details:
1. I installed PostgreSQ
Did I miss this in the README? This is not so much a bug as a migration
requirement:
Some old schemas relied on a stupid construct for creating sequences
(hey, we all have cruft), using a table rather than a sequence to create
a sequence shared by multiple tables.
Pg_dump output contains:
Hi All,
I've been using partial PGresult-s since pgsql v7.4, and one of "signs" that
it's there (after a "read" event on a non-blocking tcp connection to pgsql +
a call to PQconsumeInput) is a check: "pgconn->result != NULL", where pgconn
is a pointer to a PGconn object. Looks like in v8.2rc1,
Daniel Baldoni wrote:
>
> The following bug has been logged online:
>
> Bug reference: 2798
> Logged by: Daniel Baldoni
> Email address: [EMAIL PROTECTED]
> PostgreSQL version: 8.2rc
> Operating system: Any
> Description:Obsolete tiemzone data included
> Details:
>
Daniel Baldoni wrote:
The following bug has been logged online:
Bug reference: 2798
Logged by: Daniel Baldoni
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.2rc
Operating system: Any
Description:Obsolete tiemzone data included
Details:
G'day folks,
This m
Igor Shevchenko <[EMAIL PROTECTED]> writes:
> I've been using partial PGresult-s since pgsql v7.4, and one of "signs" that
> it's there (after a "read" event on a non-blocking tcp connection to pgsql +
> a call to PQconsumeInput) is a check: "pgconn->result != NULL", where pgconn
> is a pointer
11 matches
Mail list logo