| From: | Simon Riggs <simon(at)2ndquadrant(dot)com> |
|---|---|
| To: | Andres Freund <andres(at)anarazel(dot)de> |
| Cc: | Stas Kelvich <s(dot)kelvich(at)postgrespro(dot)ru>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Read-only access to temp tables for 2PC transactions |
| Date: | 2019-05-24 08:30:22 |
| Message-ID: | CANP8+jJiSqRL5D+EAGGtkptj4rg-JB9+mKkr6VVhYrH7CB7XWA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Thu, 23 May 2019 at 16:55, Andres Freund <andres(at)anarazel(dot)de> wrote:
> Hi,
>
> On 2019-05-23 12:36:09 +0100, Simon Riggs wrote:
> > The ONLY case where this matters is if someone does a PREPARE and then
> > starts doing other work on the session. Which makes no sense in the
> normal
> > workflow of a session. I'm sure there are tests that do that, but those
> > tests are unrepresentative of sensible usage.
>
> That's extremely common.
>
Not at all.
> There's no way we can forbid using session after 2PC unconditionally,
> it'd break most users of 2PC.
>
Since we disagree, can you provide more information about this usage
pattern?
--
Simon Riggs http://www.2ndQuadrant.com/
<http://www.2ndquadrant.com/>
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Simon Riggs | 2019-05-24 08:52:49 | Re: Read-only access to temp tables for 2PC transactions |
| Previous Message | David Rowley | 2019-05-24 08:09:46 | Re: Why does not subquery pruning conditions inherit to parent query? |