Re: cursor sensitivity misunderstanding

From: Peter Eisentraut <peter(dot)eisentraut(at)enterprisedb(dot)com>
To: "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>
Cc: pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: cursor sensitivity misunderstanding
Date: 2021-02-25 15:37:02
Message-ID: b887c836-373c-5feb-562b-2292f376cb50@enterprisedb.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 18.02.21 19:14, Peter Eisentraut wrote:
> On 18.02.21 17:11, David G. Johnston wrote:
>> The OP was doing a course based on Oracle and was confused regarding
>> our behavior.  The documentation failed to help me provide a useful
>> response, so I'd agree there is something here that needs reworking if
>> not outright fixing.
>
> According to the piece of the standard that I posted, the sensitivity
> behavior here is implementation-dependent (not even -defined), so both
> implementations are correct.
>
> But the poster was apparently also confused by the same piece of
> documentation.

I came up with the attached patch to sort this out a bit. It does not
change any cursor behavior. But the documentation now uses the terms
more correctly and explains the differences between SQL and the
PostgreSQL implementation better, I think.

Attachment Content-Type Size
0001-Fix-use-of-cursor-sensitivity-terminology.patch text/plain 16.4 KB

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Peter Eisentraut 2021-02-25 15:58:28 Re: SSL SNI
Previous Message Julien Rouhaud 2021-02-25 14:35:06 Re: archive_command / pg_stat_archiver & documentation