pg.ddx.io  pgsql-committers@postgresql.org mailing list archive  
help / color / mirror / Atom feed
pgsql: Error out if SKIP LOCKED and WITH TIES are both specified
3+ messages / 1 participants
[nested] [flat]

* pgsql: Error out if SKIP LOCKED and WITH TIES are both specified
@ 2021-10-01 21:31 Alvaro Herrera <alvherre@alvh.no-ip.org>
  0 siblings, 0 replies; 3+ messages in thread

From: Alvaro Herrera @ 2021-10-01 21:31 UTC (permalink / raw)
  To: pgsql-committers@lists.postgresql.org

Error out if SKIP LOCKED and WITH TIES are both specified

Both bugs #16676[1] and #17141[2] illustrate that the combination of
SKIP LOCKED and FETCH FIRST WITH TIES break expectations when it comes
to rows returned to other sessions accessing the same row.  Since this
situation is detectable from the syntax and hard to fix otherwise,
forbid for now, with the potential to fix in the future.

[1] https://postgr.es/m/16676-fd62c3c835880da6@postgresql.org
[2] https://postgr.es/m/17141-913d78b9675aac8e@postgresql.org

Backpatch-through: 13, where WITH TIES was introduced
Author: David Christensen <david.christensen@crunchydata.com>
Discussion: https://postgr.es/m/CAOxo6XLPccCKru3xPMaYDpa+AXyPeWFs+SskrrL+HKwDjJnLhg@mail.gmail.com

Branch
------
master

Details
-------
https://git.postgresql.org/pg/commitdiff/c6bc655ee2ef09449da7ff688a8be19a13db5c4a

Modified Files
--------------
doc/src/sgml/ref/select.sgml        |  3 ++-
src/backend/commands/matview.c      |  3 ++-
src/backend/parser/gram.y           | 15 +++++++++++++++
src/test/regress/expected/limit.out |  5 +++++
src/test/regress/sql/limit.sql      |  5 +++++
5 files changed, 29 insertions(+), 2 deletions(-)



^ permalink  raw  reply  [nested|flat] 3+ messages in thread

* pgsql: Error out if SKIP LOCKED and WITH TIES are both specified
@ 2021-10-01 21:31 Alvaro Herrera <alvherre@alvh.no-ip.org>
  0 siblings, 0 replies; 3+ messages in thread

From: Alvaro Herrera @ 2021-10-01 21:31 UTC (permalink / raw)
  To: pgsql-committers@lists.postgresql.org

Error out if SKIP LOCKED and WITH TIES are both specified

Both bugs #16676[1] and #17141[2] illustrate that the combination of
SKIP LOCKED and FETCH FIRST WITH TIES break expectations when it comes
to rows returned to other sessions accessing the same row.  Since this
situation is detectable from the syntax and hard to fix otherwise,
forbid for now, with the potential to fix in the future.

[1] https://postgr.es/m/16676-fd62c3c835880da6@postgresql.org
[2] https://postgr.es/m/17141-913d78b9675aac8e@postgresql.org

Backpatch-through: 13, where WITH TIES was introduced
Author: David Christensen <david.christensen@crunchydata.com>
Discussion: https://postgr.es/m/CAOxo6XLPccCKru3xPMaYDpa+AXyPeWFs+SskrrL+HKwDjJnLhg@mail.gmail.com

Branch
------
REL_14_STABLE

Details
-------
https://git.postgresql.org/pg/commitdiff/20047609d39cc4d30d6b266ed3a8b418b3ce5f78

Modified Files
--------------
doc/src/sgml/ref/select.sgml        |  3 ++-
src/backend/commands/matview.c      |  3 ++-
src/backend/parser/gram.y           | 15 +++++++++++++++
src/test/regress/expected/limit.out |  5 +++++
src/test/regress/sql/limit.sql      |  5 +++++
5 files changed, 29 insertions(+), 2 deletions(-)



^ permalink  raw  reply  [nested|flat] 3+ messages in thread

* pgsql: Error out if SKIP LOCKED and WITH TIES are both specified
@ 2021-10-01 21:31 Alvaro Herrera <alvherre@alvh.no-ip.org>
  0 siblings, 0 replies; 3+ messages in thread

From: Alvaro Herrera @ 2021-10-01 21:31 UTC (permalink / raw)
  To: pgsql-committers@lists.postgresql.org

Error out if SKIP LOCKED and WITH TIES are both specified

Both bugs #16676[1] and #17141[2] illustrate that the combination of
SKIP LOCKED and FETCH FIRST WITH TIES break expectations when it comes
to rows returned to other sessions accessing the same row.  Since this
situation is detectable from the syntax and hard to fix otherwise,
forbid for now, with the potential to fix in the future.

[1] https://postgr.es/m/16676-fd62c3c835880da6@postgresql.org
[2] https://postgr.es/m/17141-913d78b9675aac8e@postgresql.org

Backpatch-through: 13, where WITH TIES was introduced
Author: David Christensen <david.christensen@crunchydata.com>
Discussion: https://postgr.es/m/CAOxo6XLPccCKru3xPMaYDpa+AXyPeWFs+SskrrL+HKwDjJnLhg@mail.gmail.com

Branch
------
REL_13_STABLE

Details
-------
https://git.postgresql.org/pg/commitdiff/170206e458bce1d4be34bb805f884b2735430519

Modified Files
--------------
doc/src/sgml/ref/select.sgml        |  3 ++-
src/backend/commands/matview.c      |  3 ++-
src/backend/parser/gram.y           | 15 +++++++++++++++
src/test/regress/expected/limit.out |  5 +++++
src/test/regress/sql/limit.sql      |  5 +++++
5 files changed, 29 insertions(+), 2 deletions(-)



^ permalink  raw  reply  [nested|flat] 3+ messages in thread


end of thread, other threads:[~2021-10-01 21:31 UTC | newest]

Thread overview: 3+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2021-10-01 21:31 pgsql: Error out if SKIP LOCKED and WITH TIES are both specified Alvaro Herrera <alvherre@alvh.no-ip.org>
2021-10-01 21:31 pgsql: Error out if SKIP LOCKED and WITH TIES are both specified Alvaro Herrera <alvherre@alvh.no-ip.org>
2021-10-01 21:31 pgsql: Error out if SKIP LOCKED and WITH TIES are both specified Alvaro Herrera <alvherre@alvh.no-ip.org>

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox