Re: [PATCH] Slight improvement of worker_spi.c example - Mailing list pgsql-hackers

From Nathan Bossart
Subject Re: [PATCH] Slight improvement of worker_spi.c example
Date
Msg-id 20230612233015.GB180938@nathanxps13
Whole thread Raw
In response to Re: [PATCH] Slight improvement of worker_spi.c example  (Michael Paquier <michael@paquier.xyz>)
Responses Re: [PATCH] Slight improvement of worker_spi.c example
List pgsql-hackers
On Sat, Jun 03, 2023 at 06:35:00PM -0400, Michael Paquier wrote:
> It does not have to be complicated, but I definitely agree that we'd
> better spend some efforts in improving it as a whole especially
> knowing that this is mentioned on the docs as an example that one
> could rely on.

+1.  I know I've used worker_spi as a reference for writing background
workers before.

IMHO it'd be better if the patch documented the places where the ordering
really does matter instead of hoping extension authors will understand the
reasoning behind the proposed reordering.  I agree that the current code
could lead folks to think that PushActiveSnapshot must go after
SPI_connect, but wouldn't the reverse ordering just give folks the opposite
impression?

-- 
Nathan Bossart
Amazon Web Services: https://aws.amazon.com



pgsql-hackers by date:

Previous
From: Michael Paquier
Date:
Subject: Re: Setting restrictedtoken in pg_regress
Next
From: Nathan Bossart
Date:
Subject: Re: Setting restrictedtoken in pg_regress