RE: [PoC] pg_upgrade: allow to upgrade publisher node

From: "Hayato Kuroda (Fujitsu)" <kuroda(dot)hayato(at)fujitsu(dot)com>
To: 'vignesh C' <vignesh21(at)gmail(dot)com>
Cc: "Wei Wang (Fujitsu)" <wangw(dot)fnst(at)fujitsu(dot)com>, Peter Eisentraut <peter(dot)eisentraut(at)enterprisedb(dot)com>, Julien Rouhaud <rjuju123(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>, Peter Smith <smithpb2250(at)gmail(dot)com>
Subject: RE: [PoC] pg_upgrade: allow to upgrade publisher node
Date: 2023-06-08 03:54:46
Message-ID: TYAPR01MB586619721863B7FFDAC4369FF550A@TYAPR01MB5866.jpnprd01.prod.outlook.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Dear Vignesh,

Thank you for reviewing! PSA new version patch set.

> Few minor comments:
> 1) we could remove the variable slotname from the below code by using
> PQgetvalue directly in pg_log:
> + for (i = 0; i < ntups; i++)
> + {
> + char *slotname;
> +
> + is_error = true;
> +
> + slotname = PQgetvalue(res, i, i_slotname);
> +
> + pg_log(PG_WARNING,
> + "\nWARNING: logical replication slot \"%s\"
> is not active",
> + slotname);
> + }

Removed. Such codes were in two functions, and both of them were fixed.

> 2) This include "catalog/pg_control.h" should be after inclusion pg_collation.h
> #include "catalog/pg_authid_d.h"
> +#include "catalog/pg_control.h"
> #include "catalog/pg_collation.h"

Moved.

> 3) This spurious addition line change might not be required in this patch:
> --- a/src/bin/pg_upgrade/t/003_logical_replication_slots.pl
> +++ b/src/bin/pg_upgrade/t/003_logical_replication_slots.pl
> @@ -85,11 +85,39 @@ $old_node->safe_psql(
> ]);
>
> my $result = $old_node->safe_psql('postgres',
> - "SELECT count (*) FROM
> pg_logical_slot_get_changes('test_slot', NULL, NULL)"
> + "SELECT count(*) FROM
> pg_logical_slot_peek_changes('test_slot', NULL, NULL)"
> );
> +
> is($result, qq(12), 'ensure WALs are not consumed yet');
> $old_node->stop;

I removed the line.
In the first place, what I wanted to check here was that pg_upgrade failed because
WALs were not consumed. So if pg_logical_slot_get_changes() was called here, all
of WALs were consumed here and the subsequent command was sucseeded. This was not
happy for us and that's why changed to pg_logical_slot_peek_changes().
But after considering more, I thought that calling the function was not the mandatory
because no one needed the output.So removed.

> 4) This inclusion "#include "access/xlogrecord.h" is not required:
> #include "postgres_fe.h"
>
> +#include "access/xlogrecord.h"
> +#include "access/xlog_internal.h"
> #include "catalog/pg_authid_d.h"

Removed.

> 5)"thepublisher's" should be "the publisher's"
> When a live check is requested, there is a possibility of additional changes
> occurring, which may cause the current WAL position to exceed the
> confirmed_flush_lsn
> of the slot. As a result, we check the confirmed_flush_lsn of each logical slot
> instead. This is sufficient as all the WAL records will be sent during
> thepublisher's
> shutdown.

Fixed.

Best Regards,
Hayato Kuroda
FUJITSU LIMITED

Attachment Content-Type Size
v16-0001-pg_upgrade-Add-include-logical-replication-slots.patch application/octet-stream 32.3 KB
v16-0002-Always-persist-to-disk-logical-slots-during-a-sh.patch application/octet-stream 4.8 KB
v16-0003-pg_upgrade-Add-check-function-for-include-logica.patch application/octet-stream 5.0 KB
v16-0004-Change-the-method-used-to-check-logical-replicat.patch application/octet-stream 6.8 KB

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Amit Kapila 2023-06-08 05:05:54 Re: Support logical replication of DDLs
Previous Message Dilip Kumar 2023-06-08 03:38:34 Re: Let's make PostgreSQL multi-threaded