Re: patch for parallel pg_dump - Mailing list pgsql-hackers

From Tom Lane
Subject Re: patch for parallel pg_dump
Date
Msg-id 21689.1328632754@sss.pgh.pa.us
Whole thread Raw
In response to Re: patch for parallel pg_dump  (Robert Haas <robertmhaas@gmail.com>)
List pgsql-hackers
Robert Haas <robertmhaas@gmail.com> writes:
> most places that issue queries can simply use those routines without
> needing to peek under the hood into the ArchiveHandle.  This is not
> quite enough to get rid of g_conn, but it's close: the major stumbling
> block at this point is probably exit_nicely().  The gyrations we're
> going through to make sure that AH->connection gets closed before
> exiting are fairly annoying; maybe we should invent something in
> dumputils.c along the line of the backend's on_shmem_exit().

Do we actually care about closing the connection?  Worst case is that
backend logs an "unexpected EOF" message.  But yeah, an atexit hook
might be the easiest solution.
        regards, tom lane


pgsql-hackers by date:

Previous
From: Magnus Hagander
Date:
Subject: Re: incorrect handling of the timeout in pg_receivexlog
Next
From: Greg Smith
Date:
Subject: Re: double writes using "double-write buffer" approach [WIP]