From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
Cc: | "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Something is broken about connection startup |
Date: | 2016-11-14 15:26:32 |
Message-ID: | 30195.1479137192@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Robert Haas <robertmhaas(at)gmail(dot)com> writes:
> I assume you're going to back-patch this, and the consequences of
> failing to reset it before going idle could easily be vastly worse
> than the problem you're trying to fix. So I'd rather not make
> assumptions like "the client will probably never sleep between Bind
> and Execute". I bet that's actually false, and I certainly wouldn't
> want to bet the farm on it being true.
No, I'm not at all proposing to assume that. But I may be willing to
assume that "we don't hold a CatalogSnapshot between Bind and Execute
unless we're also holding a transaction snapshot". I need to do a bit
more research to see if that's actually true, though.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Robert Haas | 2016-11-14 15:31:36 | Re: [bug fix] Cascading standby cannot catch up and get stuck emitting the same message repeatedly |
Previous Message | Tom Lane | 2016-11-14 15:23:12 | Re: Pinning a buffer in TupleTableSlot is unnecessary |