Re: GenBKI emits useless open;close for catalogs without rows - Mailing list pgsql-hackers

From Peter Eisentraut
Subject Re: GenBKI emits useless open;close for catalogs without rows
Date
Msg-id 3047ac73-5a4e-47d4-85c9-fefc0ff846f2@eisentraut.org
Whole thread Raw
In response to Re: GenBKI emits useless open;close for catalogs without rows  (Heikki Linnakangas <hlinnaka@iki.fi>)
Responses Re: GenBKI emits useless open;close for catalogs without rows
List pgsql-hackers
On 19.09.23 20:05, Heikki Linnakangas wrote:
> One thing caught my eye though: We currently have an "open" command 
> after every "create". Except for bootstrap relations; creating a 
> bootstrap relation opens it implicitly. That seems like a weird 
> inconsistency. If we make "create" to always open the relation, we can 
> both make it more consistent and save a few lines. That's maybe worth 
> doing, per the attached. It removes the "open" command altogether, as 
> it's not needed anymore.

This seems like a good improvement to me.

It would restrict the bootstrap language so that you can only manipulate 
a table right after creating it, but I don't see why that wouldn't be 
sufficient.




pgsql-hackers by date:

Previous
From: "Drouvot, Bertrand"
Date:
Subject: Re: Synchronizing slots from primary to standby
Next
From: Peter Eisentraut
Date:
Subject: Re: GenBKI emits useless open;close for catalogs without rows