pg.ddx.io  pgsql-hackers@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Alvaro Herrera <alvherre@2ndquadrant.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Michael Paquier <michael@paquier.xyz>
Cc: pgsql-hackers@lists.postgresql.org
Subject: Re: Gripes about walsender command processing
Date: Wed, 16 Sep 2020 19:14:22 -0300
Message-ID: <20200916221422.GA24095@alvherre.pgsql> (raw)
In-Reply-To: <1633417.1600274669@sss.pgh.pa.us>

On 2020-Sep-16, Tom Lane wrote:

> This looks moderately reasonable to me.  However, with the process
> title reporting I want to add, we're going to end up with a switch
> that looks like
> 
>  		case T_IdentifySystemCmd:
> +			set_ps_display("IDENTIFY_SYSTEM");
>  			IdentifySystem();
> +			EndReplicationCommand("IDENTIFY_SYSTEM");
>  			break;
>  
>  		case T_BaseBackupCmd:
> +			set_ps_display("BASE_BACKUP");
>  			PreventInTransactionBlock(true, "BASE_BACKUP");
>  			SendBaseBackup((BaseBackupCmd *) cmd_node);
> +			EndReplicationCommand("BASE_BACKUP");
>  			break;
> 
> which is starting to look a bit repetitive and copy-pasteo-prone.

Agreed.

> I don't see an easy way to improve on it though.  The only obvious
> alternative would be to put another switch before the main one that
> just fills a "const char *cmdtag" variable, but that seems ugly.

The alternative of doing the assignment in each case of the same switch
does not look too terrible:

 		case T_IdentifySystemCmd:
+			cmdtag = "IDENTIFY_SYSTEM";
+			set_ps_display(cmdtag);
 			IdentifySystem();
+			EndReplicationCommand(cmdtag);
 			break;
 
 		case T_BaseBackupCmd:
+			cmdtag = "BASE_BACKUP";
+			set_ps_display(cmdtag);
 			PreventInTransactionBlock(true, cmdtag);
 			SendBaseBackup((BaseBackupCmd *) cmd_node);
+			EndReplicationCommand(cmdtag);
 			break;


-- 
Álvaro Herrera                https://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services





view thread (16+ messages)  latest in thread

Message-ID: <20200916221422.GA24095@alvherre.pgsql>
Permalink:  ../20200916221422.GA24095@alvherre.pgsql/
Also on:    postgresql.org/message-id/20200916221422.GA24095@alvherre.pgsql

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-hackers@postgresql.org
  Cc: alvherre@2ndquadrant.com, tgl@sss.pgh.pa.us, michael@paquier.xyz, pgsql-hackers@lists.postgresql.org
  Subject: Re: Gripes about walsender command processing
  In-Reply-To: <20200916221422.GA24095@alvherre.pgsql>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

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