Re: [HACKERS] Cached plans and statement generalization - Mailing list pgsql-hackers

From Robert Haas
Subject Re: [HACKERS] Cached plans and statement generalization
Date
Msg-id CA+TgmoaAY+nSoRaiosu_yey89pg2pXw_cBt4r=x=yXxh5LBAzQ@mail.gmail.com
Whole thread Raw
In response to Re: [HACKERS] Cached plans and statement generalization  (Konstantin Knizhnik <k.knizhnik@postgrespro.ru>)
Responses Re: [HACKERS] Cached plans and statement generalization  (Konstantin Knizhnik <k.knizhnik@postgrespro.ru>)
List pgsql-hackers
On Wed, May 10, 2017 at 12:11 PM, Konstantin Knizhnik
<k.knizhnik@postgrespro.ru> wrote:
> Robert, can you please explain why using TRY/CATCH is not safe here:
>>
>> This is definitely not a safe way of using TRY/CATCH.

This has been discussed many, many times on this mailing list before,
and I don't really want to go over it again here.  We really need a
README or some documentation about this so that we don't have to keep
answering this same question again and again.

-- 
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company



pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: [HACKERS] bumping HASH_VERSION to 3
Next
From: David Fetter
Date:
Subject: Re: [HACKERS] Hash Functions