Re: Not quite a security hole in internal_in

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Andrew Dunstan <andrew(at)dunslane(dot)net>
Cc: pgsql-hackers(at)postgreSQL(dot)org
Subject: Re: Not quite a security hole in internal_in
Date: 2009-06-09 17:44:16
Message-ID: 23271.1244569456@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Andrew Dunstan <andrew(at)dunslane(dot)net> writes:
> Tom Lane wrote:
>> This will ensure the fix is in place and protecting future coding,
>> although possibly not getting enforced in 8.4 production instances that
>> were upgraded from beta (if there are any such).

> How common is this scenario? It's certainly not something I ever do.

I would agree that it should be pretty darn rare. But even so, this
is not a fix for an immediate bug but just safety against possible
future bugs. So even if there is somebody out there who manages to miss
having the fix, I think they are not at serious risk.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2009-06-09 17:47:14 Re: [HACKERS] Cursor with hold emits the same row more than once across commits in 8.3.7
Previous Message Alvaro Herrera 2009-06-09 17:38:51 Re: [HACKERS] Cursor with hold emits the same row more than once across commits in 8.3.7