Hi Richard,
Thanks for the reply -- yeah, I know it's and old version but management has been reluctant to update a production database.
As for the logs, I looked around an didn't see any. pg_ctl start is not using the -l option for logging and output is redirected to /dev/null :(
Anyway, now I have some room to update, which leads to the following questions:
1) I'm assuming that if I update 7.3.2 to 7.3.15 I can leave the data in place (that is, without doing a dump/restore) -- is this correct?
2) If I up upgrade to 8.x can just copy the data files or do I have to do a dump/restore? The latter would be hard since pg_dump also fails on this same table and pg_dump doesn't seem to have an 'ignore table' option.
Mark
On 10/6/06, Richard Huxton <dev@archonet.com> wrote: Mark Greenbank wrote:
> # psql --version
> psql (PostgreSQL) 7.3.2
May I be the first to say "GODS ALIVE MAN! WHAT ARE YOU STILL DOING
RUNNING 7.3.2!". Even if you can't upgrade from 7.3, the latest release
is 7.3.15 - that's 13 sets of bug-fixes you're ignoring. There's a
passing chance one of those bugs might be responsible for your error.
> contains support for command-line editing
>
> # psql
> mncis2-rel=# select count(*) from members;
> count
> -------
> 22676
> (1 row)
>
> mncis2-rel=# select count(*) from email_queue;
> server closed the connection unexpectedly
> This probably means the server terminated abnormally
> before or while processing the request.
> The connection to the server was lost. Attempting reset: Failed.
What do the logs say?
--
Richard Huxton
Archonet Ltd