pg.ddx.io  pgsql-committers@postgresql.org mailing list archive  
help / color / mirror / Atom feed
pgsql: Make multixact error message more explicit
6+ messages / 1 participants
[nested] [flat]

* pgsql: Make multixact error message more explicit
@ 2022-11-24 09:46 Alvaro Herrera <alvherre@alvh.no-ip.org>
  0 siblings, 0 replies; 6+ messages in thread

From: Alvaro Herrera @ 2022-11-24 09:46 UTC (permalink / raw)
  To: pgsql-committers@lists.postgresql.org

Make multixact error message more explicit

There are recent reports involving a very old error message that we have
no history of hitting -- perhaps a recently introduced bug.  Improve the
error message in an attempt to improve our chances of investigating the
bug.

Per reports from Dimos Stamatakis and Bob Krier.

Backpatch to 11.

Discussion: https://postgr.es/m/CO2PR0801MB2310579F65529380A4E5EDC0E20A9@CO2PR0801MB2310.namprd08.prod.outlook.c...
Discussion: https://postgr.es/m/17518-04e368df5ad7f2ee@postgresql.org

Branch
------
master

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

Modified Files
--------------
src/backend/access/transam/multixact.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)



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

* pgsql: Make multixact error message more explicit
@ 2022-11-24 09:46 Alvaro Herrera <alvherre@alvh.no-ip.org>
  0 siblings, 0 replies; 6+ messages in thread

From: Alvaro Herrera @ 2022-11-24 09:46 UTC (permalink / raw)
  To: pgsql-committers@lists.postgresql.org

Make multixact error message more explicit

There are recent reports involving a very old error message that we have
no history of hitting -- perhaps a recently introduced bug.  Improve the
error message in an attempt to improve our chances of investigating the
bug.

Per reports from Dimos Stamatakis and Bob Krier.

Backpatch to 11.

Discussion: https://postgr.es/m/CO2PR0801MB2310579F65529380A4E5EDC0E20A9@CO2PR0801MB2310.namprd08.prod.outlook.c...
Discussion: https://postgr.es/m/17518-04e368df5ad7f2ee@postgresql.org

Branch
------
REL_15_STABLE

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

Modified Files
--------------
src/backend/access/transam/multixact.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)



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

* pgsql: Make multixact error message more explicit
@ 2022-11-24 09:46 Alvaro Herrera <alvherre@alvh.no-ip.org>
  0 siblings, 0 replies; 6+ messages in thread

From: Alvaro Herrera @ 2022-11-24 09:46 UTC (permalink / raw)
  To: pgsql-committers@lists.postgresql.org

Make multixact error message more explicit

There are recent reports involving a very old error message that we have
no history of hitting -- perhaps a recently introduced bug.  Improve the
error message in an attempt to improve our chances of investigating the
bug.

Per reports from Dimos Stamatakis and Bob Krier.

Backpatch to 11.

Discussion: https://postgr.es/m/CO2PR0801MB2310579F65529380A4E5EDC0E20A9@CO2PR0801MB2310.namprd08.prod.outlook.c...
Discussion: https://postgr.es/m/17518-04e368df5ad7f2ee@postgresql.org

Branch
------
REL_14_STABLE

Details
-------
https://git.postgresql.org/pg/commitdiff/8e7c86785a11cd3e56f895b8e2a489546c36a350

Modified Files
--------------
src/backend/access/transam/multixact.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)



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

* pgsql: Make multixact error message more explicit
@ 2022-11-24 09:46 Alvaro Herrera <alvherre@alvh.no-ip.org>
  0 siblings, 0 replies; 6+ messages in thread

From: Alvaro Herrera @ 2022-11-24 09:46 UTC (permalink / raw)
  To: pgsql-committers@lists.postgresql.org

Make multixact error message more explicit

There are recent reports involving a very old error message that we have
no history of hitting -- perhaps a recently introduced bug.  Improve the
error message in an attempt to improve our chances of investigating the
bug.

Per reports from Dimos Stamatakis and Bob Krier.

Backpatch to 11.

Discussion: https://postgr.es/m/CO2PR0801MB2310579F65529380A4E5EDC0E20A9@CO2PR0801MB2310.namprd08.prod.outlook.c...
Discussion: https://postgr.es/m/17518-04e368df5ad7f2ee@postgresql.org

Branch
------
REL_13_STABLE

Details
-------
https://git.postgresql.org/pg/commitdiff/5a185246f9a742371a75ac0e3a95d0ceba9494e5

Modified Files
--------------
src/backend/access/transam/multixact.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)



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

* pgsql: Make multixact error message more explicit
@ 2022-11-24 09:46 Alvaro Herrera <alvherre@alvh.no-ip.org>
  0 siblings, 0 replies; 6+ messages in thread

From: Alvaro Herrera @ 2022-11-24 09:46 UTC (permalink / raw)
  To: pgsql-committers@lists.postgresql.org

Make multixact error message more explicit

There are recent reports involving a very old error message that we have
no history of hitting -- perhaps a recently introduced bug.  Improve the
error message in an attempt to improve our chances of investigating the
bug.

Per reports from Dimos Stamatakis and Bob Krier.

Backpatch to 11.

Discussion: https://postgr.es/m/CO2PR0801MB2310579F65529380A4E5EDC0E20A9@CO2PR0801MB2310.namprd08.prod.outlook.c...
Discussion: https://postgr.es/m/17518-04e368df5ad7f2ee@postgresql.org

Branch
------
REL_12_STABLE

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

Modified Files
--------------
src/backend/access/transam/multixact.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)



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

* pgsql: Make multixact error message more explicit
@ 2022-11-24 09:46 Alvaro Herrera <alvherre@alvh.no-ip.org>
  0 siblings, 0 replies; 6+ messages in thread

From: Alvaro Herrera @ 2022-11-24 09:46 UTC (permalink / raw)
  To: pgsql-committers@lists.postgresql.org

Make multixact error message more explicit

There are recent reports involving a very old error message that we have
no history of hitting -- perhaps a recently introduced bug.  Improve the
error message in an attempt to improve our chances of investigating the
bug.

Per reports from Dimos Stamatakis and Bob Krier.

Backpatch to 11.

Discussion: https://postgr.es/m/CO2PR0801MB2310579F65529380A4E5EDC0E20A9@CO2PR0801MB2310.namprd08.prod.outlook.c...
Discussion: https://postgr.es/m/17518-04e368df5ad7f2ee@postgresql.org

Branch
------
REL_11_STABLE

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

Modified Files
--------------
src/backend/access/transam/multixact.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)



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


end of thread, other threads:[~2022-11-24 09:46 UTC | newest]

Thread overview: 6+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2022-11-24 09:46 pgsql: Make multixact error message more explicit Alvaro Herrera <alvherre@alvh.no-ip.org>
2022-11-24 09:46 pgsql: Make multixact error message more explicit Alvaro Herrera <alvherre@alvh.no-ip.org>
2022-11-24 09:46 pgsql: Make multixact error message more explicit Alvaro Herrera <alvherre@alvh.no-ip.org>
2022-11-24 09:46 pgsql: Make multixact error message more explicit Alvaro Herrera <alvherre@alvh.no-ip.org>
2022-11-24 09:46 pgsql: Make multixact error message more explicit Alvaro Herrera <alvherre@alvh.no-ip.org>
2022-11-24 09:46 pgsql: Make multixact error message more explicit 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