The following bug has been logged online:
Bug reference: 4738
Logged by: Jonathan Barnhart
Email address: jdbarnh...@yahoo.com
PostgreSQL version: 8.3.7
Operating system: WinXP, Vista
Description:Cannot reconnect to shared memory
Details:
This bug seems to have been
On Fri, 2009-03-27 at 15:43 -0400, Tom Lane wrote:
> Heikki Linnakangas writes:
> > I'm not too familiar with this code, but I think we could just enable
> > ImmediateInterruptOK in CopyGetData().
>
> Only if you are wanting to break things.
>
Doesn't DoingCommandRead protect us in the SIGINT
On Fri, 2009-03-27 at 15:43 -0400, Tom Lane wrote:
> Heikki Linnakangas writes:
> > I'm not too familiar with this code, but I think we could just enable
> > ImmediateInterruptOK in CopyGetData().
>
> Only if you are wanting to break things.
>
> The reason we don't allow client read to be inter
Heikki Linnakangas writes:
> I'm not too familiar with this code, but I think we could just enable
> ImmediateInterruptOK in CopyGetData().
Only if you are wanting to break things.
The reason we don't allow client read to be interrupted is the fear of
losing protocol sync on an incomplete messa
Jeff Davis wrote:
"SIGINT -- The server disallows new connections and sends all existing
server processes SIGTERM, which will cause them to abort their current
transactions and exit promptly."
http://www.postgresql.org/docs/8.3/static/server-shutdown.html
If you have an open COPY and no data is
Jeff Davis wrote:
The docs say:
"SIGINT -- The server disallows new connections and sends all existing
server processes SIGTERM, which will cause them to abort their current
transactions and exit promptly."
http://www.postgresql.org/docs/8.3/static/server-shutdown.html
If you have an open COPY
On Thu, 2009-03-26 at 21:45 -0400, Bruce Momjian wrote:
> > http://archives.postgresql.org/pgsql-bugs/2009-03/msg00062.php
> >
> > It may or may not be a real bug, but I didn't receive any response. If
> > you think it might be a bug, can you please add it to the open items?
>
> Hmm, odd I don't
