pg.ddx.io  pgsql-committers@postgresql.org mailing list archive  
help / color / mirror / Atom feed
pgbulkload - pgbulkload: ParallelWriter should have transferred server
7+ messages / 2 participants
[nested] [flat]

* pgbulkload - pgbulkload: ParallelWriter should have transferred server
@ 2009-06-15 09:46 User Itagaki <itagaki@pgfoundry.org>
  0 siblings, 0 replies; 7+ messages in thread

From: itagaki@pgfoundry.org @ 2009-06-15 09:46 UTC (permalink / raw)
  To: pgsql-committers

Log Message:
-----------
ParallelWriter should have transferred server messages to client.

Modified Files:
--------------
    pgbulkload/bin/expected:
        load_parallel.out (r1.2 -> r1.3)
        (http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/pgbulkload/pgbulkload/bin/expected/load_parallel.out?r1=...)
    pgbulkload/lib:
        pg_strutil.c (r1.4 -> r1.5)
        (http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/pgbulkload/pgbulkload/lib/pg_strutil.c?r1=1.4&r2=1.5)
        writer_parallel.c (r1.2 -> r1.3)
        (http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/pgbulkload/pgbulkload/lib/writer_parallel.c?r1=1.2&r...)




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

* pgsql: Close race condition between datfrozen and relfrozen updates.
@ 2024-04-29 17:30 Noah Misch <noah@leadboat.com>
  0 siblings, 0 replies; 7+ messages in thread

From: Noah Misch @ 2024-04-29 17:30 UTC (permalink / raw)
  To: pgsql-committers@lists.postgresql.org

Close race condition between datfrozen and relfrozen updates.

vac_update_datfrozenxid() did multiple loads of relfrozenxid and
relminmxid from buffer memory, and it assumed each would get the same
value.  Not so if a concurrent vac_update_relstats() did an inplace
update.  Commit 2d2e40e3befd8b9e0d2757554537345b15fa6ea2 fixed the same
kind of bug in vac_truncate_clog().  Today's bug could cause the
rel-level field and XIDs in the rel's rows to precede the db-level
field.  A cluster having such values should VACUUM affected tables.
Back-patch to v12 (all supported versions).

Discussion: https://postgr.es/m/20240423003956.e7.nmisch@google.com

Branch
------
master

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

Modified Files
--------------
src/backend/commands/vacuum.c | 28 ++++++++++++++++------------
1 file changed, 16 insertions(+), 12 deletions(-)



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

* pgsql: Close race condition between datfrozen and relfrozen updates.
@ 2024-04-29 17:30 Noah Misch <noah@leadboat.com>
  0 siblings, 0 replies; 7+ messages in thread

From: Noah Misch @ 2024-04-29 17:30 UTC (permalink / raw)
  To: pgsql-committers@lists.postgresql.org

Close race condition between datfrozen and relfrozen updates.

vac_update_datfrozenxid() did multiple loads of relfrozenxid and
relminmxid from buffer memory, and it assumed each would get the same
value.  Not so if a concurrent vac_update_relstats() did an inplace
update.  Commit 2d2e40e3befd8b9e0d2757554537345b15fa6ea2 fixed the same
kind of bug in vac_truncate_clog().  Today's bug could cause the
rel-level field and XIDs in the rel's rows to precede the db-level
field.  A cluster having such values should VACUUM affected tables.
Back-patch to v12 (all supported versions).

Discussion: https://postgr.es/m/20240423003956.e7.nmisch@google.com

Branch
------
REL_16_STABLE

Details
-------
https://git.postgresql.org/pg/commitdiff/92685c389d5416f87553bfb80205d79d5670a695

Modified Files
--------------
src/backend/commands/vacuum.c | 28 ++++++++++++++++------------
1 file changed, 16 insertions(+), 12 deletions(-)



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

* pgsql: Close race condition between datfrozen and relfrozen updates.
@ 2024-04-29 17:30 Noah Misch <noah@leadboat.com>
  0 siblings, 0 replies; 7+ messages in thread

From: Noah Misch @ 2024-04-29 17:30 UTC (permalink / raw)
  To: pgsql-committers@lists.postgresql.org

Close race condition between datfrozen and relfrozen updates.

vac_update_datfrozenxid() did multiple loads of relfrozenxid and
relminmxid from buffer memory, and it assumed each would get the same
value.  Not so if a concurrent vac_update_relstats() did an inplace
update.  Commit 2d2e40e3befd8b9e0d2757554537345b15fa6ea2 fixed the same
kind of bug in vac_truncate_clog().  Today's bug could cause the
rel-level field and XIDs in the rel's rows to precede the db-level
field.  A cluster having such values should VACUUM affected tables.
Back-patch to v12 (all supported versions).

Discussion: https://postgr.es/m/20240423003956.e7.nmisch@google.com

Branch
------
REL_15_STABLE

Details
-------
https://git.postgresql.org/pg/commitdiff/7c5915c4b16c965124a36615ec54cca501a212a9

Modified Files
--------------
src/backend/commands/vacuum.c | 28 ++++++++++++++++------------
1 file changed, 16 insertions(+), 12 deletions(-)



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

* pgsql: Close race condition between datfrozen and relfrozen updates.
@ 2024-04-29 17:30 Noah Misch <noah@leadboat.com>
  0 siblings, 0 replies; 7+ messages in thread

From: Noah Misch @ 2024-04-29 17:30 UTC (permalink / raw)
  To: pgsql-committers@lists.postgresql.org

Close race condition between datfrozen and relfrozen updates.

vac_update_datfrozenxid() did multiple loads of relfrozenxid and
relminmxid from buffer memory, and it assumed each would get the same
value.  Not so if a concurrent vac_update_relstats() did an inplace
update.  Commit 2d2e40e3befd8b9e0d2757554537345b15fa6ea2 fixed the same
kind of bug in vac_truncate_clog().  Today's bug could cause the
rel-level field and XIDs in the rel's rows to precede the db-level
field.  A cluster having such values should VACUUM affected tables.
Back-patch to v12 (all supported versions).

Discussion: https://postgr.es/m/20240423003956.e7.nmisch@google.com

Branch
------
REL_14_STABLE

Details
-------
https://git.postgresql.org/pg/commitdiff/2ca19aa8165c6bec84c1d527fc5f3100c2161b1a

Modified Files
--------------
src/backend/commands/vacuum.c | 28 ++++++++++++++++------------
1 file changed, 16 insertions(+), 12 deletions(-)



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

* pgsql: Close race condition between datfrozen and relfrozen updates.
@ 2024-04-29 17:30 Noah Misch <noah@leadboat.com>
  0 siblings, 0 replies; 7+ messages in thread

From: Noah Misch @ 2024-04-29 17:30 UTC (permalink / raw)
  To: pgsql-committers@lists.postgresql.org

Close race condition between datfrozen and relfrozen updates.

vac_update_datfrozenxid() did multiple loads of relfrozenxid and
relminmxid from buffer memory, and it assumed each would get the same
value.  Not so if a concurrent vac_update_relstats() did an inplace
update.  Commit 2d2e40e3befd8b9e0d2757554537345b15fa6ea2 fixed the same
kind of bug in vac_truncate_clog().  Today's bug could cause the
rel-level field and XIDs in the rel's rows to precede the db-level
field.  A cluster having such values should VACUUM affected tables.
Back-patch to v12 (all supported versions).

Discussion: https://postgr.es/m/20240423003956.e7.nmisch@google.com

Branch
------
REL_13_STABLE

Details
-------
https://git.postgresql.org/pg/commitdiff/70cadfba0c70b25922d0739a9e09d24f0efd7f46

Modified Files
--------------
src/backend/commands/vacuum.c | 28 ++++++++++++++++------------
1 file changed, 16 insertions(+), 12 deletions(-)



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

* pgsql: Close race condition between datfrozen and relfrozen updates.
@ 2024-04-29 17:30 Noah Misch <noah@leadboat.com>
  0 siblings, 0 replies; 7+ messages in thread

From: Noah Misch @ 2024-04-29 17:30 UTC (permalink / raw)
  To: pgsql-committers@lists.postgresql.org

Close race condition between datfrozen and relfrozen updates.

vac_update_datfrozenxid() did multiple loads of relfrozenxid and
relminmxid from buffer memory, and it assumed each would get the same
value.  Not so if a concurrent vac_update_relstats() did an inplace
update.  Commit 2d2e40e3befd8b9e0d2757554537345b15fa6ea2 fixed the same
kind of bug in vac_truncate_clog().  Today's bug could cause the
rel-level field and XIDs in the rel's rows to precede the db-level
field.  A cluster having such values should VACUUM affected tables.
Back-patch to v12 (all supported versions).

Discussion: https://postgr.es/m/20240423003956.e7.nmisch@google.com

Branch
------
REL_12_STABLE

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

Modified Files
--------------
src/backend/commands/vacuum.c | 28 ++++++++++++++++------------
1 file changed, 16 insertions(+), 12 deletions(-)



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


end of thread, other threads:[~2024-04-29 17:30 UTC | newest]

Thread overview: 7+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2009-06-15 09:46 pgbulkload - pgbulkload: ParallelWriter should have transferred server User Itagaki <itagaki@pgfoundry.org>
2024-04-29 17:30 pgsql: Close race condition between datfrozen and relfrozen updates. Noah Misch <noah@leadboat.com>
2024-04-29 17:30 pgsql: Close race condition between datfrozen and relfrozen updates. Noah Misch <noah@leadboat.com>
2024-04-29 17:30 pgsql: Close race condition between datfrozen and relfrozen updates. Noah Misch <noah@leadboat.com>
2024-04-29 17:30 pgsql: Close race condition between datfrozen and relfrozen updates. Noah Misch <noah@leadboat.com>
2024-04-29 17:30 pgsql: Close race condition between datfrozen and relfrozen updates. Noah Misch <noah@leadboat.com>
2024-04-29 17:30 pgsql: Close race condition between datfrozen and relfrozen updates. Noah Misch <noah@leadboat.com>

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