pg.ddx.io  pgsql-committers@postgresql.org mailing list archive  
help / color / mirror / Atom feed
pgsql: Backpatch 031_recovery_conflict.pl.
5+ messages / 1 participants
[nested] [flat]

* pgsql: Backpatch 031_recovery_conflict.pl.
@ 2022-05-03 01:41 Andres Freund <andres@anarazel.de>
  0 siblings, 0 replies; 5+ messages in thread

From: Andres Freund @ 2022-05-03 01:41 UTC (permalink / raw)
  To: pgsql-committers@lists.postgresql.org

Backpatch 031_recovery_conflict.pl.

The prior commit showed that the introduction of recovery conflict tests was a
good idea. Without these tests it's hard to know that the fix didn't break
something...

031_recovery_conflict.pl was introduced in 9f8a050f68d and extended in
21e184403bf.

Discussion: https://postgr.es/m/20220413002626.udl7lll7f3o7nre7@alap3.anarazel.de
Backpatch: 10-14

Branch
------
REL_14_STABLE

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

Modified Files
--------------
src/test/recovery/t/031_recovery_conflict.pl | 371 +++++++++++++++++++++++++++
1 file changed, 371 insertions(+)



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

* pgsql: Backpatch 031_recovery_conflict.pl.
@ 2022-05-03 01:41 Andres Freund <andres@anarazel.de>
  0 siblings, 0 replies; 5+ messages in thread

From: Andres Freund @ 2022-05-03 01:41 UTC (permalink / raw)
  To: pgsql-committers@lists.postgresql.org

Backpatch 031_recovery_conflict.pl.

The prior commit showed that the introduction of recovery conflict tests was a
good idea. Without these tests it's hard to know that the fix didn't break
something...

031_recovery_conflict.pl was introduced in 9f8a050f68d and extended in
21e184403bf.

Discussion: https://postgr.es/m/20220413002626.udl7lll7f3o7nre7@alap3.anarazel.de
Backpatch: 10-14

Branch
------
REL_13_STABLE

Details
-------
https://git.postgresql.org/pg/commitdiff/0446d3bf3909247f06de9b8f08a739caf7cc72ca

Modified Files
--------------
src/test/recovery/t/031_recovery_conflict.pl | 371 +++++++++++++++++++++++++++
1 file changed, 371 insertions(+)



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

* pgsql: Backpatch 031_recovery_conflict.pl.
@ 2022-05-03 01:41 Andres Freund <andres@anarazel.de>
  0 siblings, 0 replies; 5+ messages in thread

From: Andres Freund @ 2022-05-03 01:41 UTC (permalink / raw)
  To: pgsql-committers@lists.postgresql.org

Backpatch 031_recovery_conflict.pl.

The prior commit showed that the introduction of recovery conflict tests was a
good idea. Without these tests it's hard to know that the fix didn't break
something...

031_recovery_conflict.pl was introduced in 9f8a050f68d and extended in
21e184403bf.

Discussion: https://postgr.es/m/20220413002626.udl7lll7f3o7nre7@alap3.anarazel.de
Backpatch: 10-14

Branch
------
REL_12_STABLE

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

Modified Files
--------------
src/test/recovery/t/031_recovery_conflict.pl | 371 +++++++++++++++++++++++++++
1 file changed, 371 insertions(+)



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

* pgsql: Backpatch 031_recovery_conflict.pl.
@ 2022-05-03 01:41 Andres Freund <andres@anarazel.de>
  0 siblings, 0 replies; 5+ messages in thread

From: Andres Freund @ 2022-05-03 01:41 UTC (permalink / raw)
  To: pgsql-committers@lists.postgresql.org

Backpatch 031_recovery_conflict.pl.

The prior commit showed that the introduction of recovery conflict tests was a
good idea. Without these tests it's hard to know that the fix didn't break
something...

031_recovery_conflict.pl was introduced in 9f8a050f68d and extended in
21e184403bf.

Discussion: https://postgr.es/m/20220413002626.udl7lll7f3o7nre7@alap3.anarazel.de
Backpatch: 10-14

Branch
------
REL_11_STABLE

Details
-------
https://git.postgresql.org/pg/commitdiff/25d5494e284104b626fdf9005117eb53ebd30df1

Modified Files
--------------
src/test/recovery/t/031_recovery_conflict.pl | 371 +++++++++++++++++++++++++++
1 file changed, 371 insertions(+)



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

* pgsql: Backpatch 031_recovery_conflict.pl.
@ 2022-05-03 01:41 Andres Freund <andres@anarazel.de>
  0 siblings, 0 replies; 5+ messages in thread

From: Andres Freund @ 2022-05-03 01:41 UTC (permalink / raw)
  To: pgsql-committers@lists.postgresql.org

Backpatch 031_recovery_conflict.pl.

The prior commit showed that the introduction of recovery conflict tests was a
good idea. Without these tests it's hard to know that the fix didn't break
something...

031_recovery_conflict.pl was introduced in 9f8a050f68d and extended in
21e184403bf.

Discussion: https://postgr.es/m/20220413002626.udl7lll7f3o7nre7@alap3.anarazel.de
Backpatch: 10-14

Branch
------
REL_10_STABLE

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

Modified Files
--------------
src/test/recovery/t/031_recovery_conflict.pl | 371 +++++++++++++++++++++++++++
1 file changed, 371 insertions(+)



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


end of thread, other threads:[~2022-05-03 01:41 UTC | newest]

Thread overview: 5+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2022-05-03 01:41 pgsql: Backpatch 031_recovery_conflict.pl. Andres Freund <andres@anarazel.de>
2022-05-03 01:41 pgsql: Backpatch 031_recovery_conflict.pl. Andres Freund <andres@anarazel.de>
2022-05-03 01:41 pgsql: Backpatch 031_recovery_conflict.pl. Andres Freund <andres@anarazel.de>
2022-05-03 01:41 pgsql: Backpatch 031_recovery_conflict.pl. Andres Freund <andres@anarazel.de>
2022-05-03 01:41 pgsql: Backpatch 031_recovery_conflict.pl. Andres Freund <andres@anarazel.de>

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