Robert Voinea writes:
>>> The problem is that after I update a table whenever I use a function that
>>> makes use of dblink_build_sql the server crashes.
FYI, I've committed patches to deal with this and some related issues.
regards, tom lane
--
Sent via pgsql-admin mai
Kevin Grittner ha scritto:
Silvio Brandani wrote:
We have a standby database
During pg_dump
Hmm... I just noticed that word "standby" in there. Can you
elaborate on what you mean by that?
-Kevin
It means it is an istance refreshed (via rsync) from another istanc
Kevin Grittner ha scritto:
Silvio Brandani wrote:
We have a standby database
During pg_dump
Hmm... I just noticed that word "standby" in there. Can you
elaborate on what you mean by that?
-Kevin
It means it is an istance refreshed (via rsync) from another istanc
Silvio Brandani wrote:
> We have a standby database
> During pg_dump
Hmm... I just noticed that word "standby" in there. Can you
elaborate on what you mean by that?
-Kevin
--
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes to your subscription:
http://www
Silvio Brandani wrote:
> We have a standby database version postgres 8.3.1 on linux .
You should seriously consider upgrading to a more recent 8.3 bug fix
release. The most current is now 8.3.11. Please read this:
http://www.postgresql.org/support/versioning
There was a bug fix related t
We have a standby database version postgres 8.3.1 on linux .
During pg_dump we get the error:
-- pg_dump: SQL command failed
-- pg_dump: Error message from server: ERROR: missing chunk number 0
for toast value 254723406
-- pg_dump: The command was: COPY helpdesk.attachments_data (id,
filedata,
