Re: Question regarding Sync message and unnamed portal

From: Bruce Momjian <bruce(at)momjian(dot)us>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Robert Haas <robertmhaas(at)gmail(dot)com>, Tatsuo Ishii <ishii(at)postgresql(dot)org>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Question regarding Sync message and unnamed portal
Date: 2013-01-25 20:32:07
Message-ID: 20130125203207.GO6848@momjian.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Fri, Jan 25, 2013 at 03:29:17PM -0500, Tom Lane wrote:
> Bruce Momjian <bruce(at)momjian(dot)us> writes:
> > Oops, thanks. Here is the right paragraph, same issue:
>
> > If successfully created, a named portal object lasts till the end of the
> > current transaction, unless explicitly destroyed. An unnamed portal is
> > destroyed at the end of the transaction, or as soon as the next Bind
> > statement specifying the unnamed portal as destination is issued. (Note
>
> What is the issue exactly? Seems clear and correct to me ... but then,
> I think I wrote this text, a long time ago.

Tatsuo's complain was that on sentence said "named portal", while all
portals are closed on transaction end. However, "unnamed portal" is
named in the next sentence, so it seems OK.

--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com

+ It's impossible for everything to be true. +

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2013-01-25 20:35:59 Re: setting per-database/role parameters checks them against wrong context
Previous Message Robert Haas 2013-01-25 20:29:58 Re: Enabling Checksums