Re: proposal: schema variables - Mailing list pgsql-hackers

From Pavel Stehule
Subject Re: proposal: schema variables
Date
Msg-id CAFj8pRA9kLgW24cX+O7XUajepQLR+MjvRDC=02O8cBcB9=0wKA@mail.gmail.com
Whole thread Raw
In response to Re: proposal: schema variables  (Pavel Stehule <pavel.stehule@gmail.com>)
Responses Re: proposal: schema variables
List pgsql-hackers


pá 20. 3. 2020 v 8:18 odesílatel Pavel Stehule <pavel.stehule@gmail.com> napsal:


čt 19. 3. 2020 v 10:43 odesílatel DUVAL REMI <REMI.DUVAL@cheops.fr> napsal:

Hello

 

I played around with the ALTER VARIABLE statement to make sure it’s OK and it seems fine to me.

 

Another last thing before commiting.

 

I agree with Thomas Vondra, that this part might/should be simplified :

 

[ { ON COMMIT DROP | ON { TRANSACTIONAL | TRANSACTION } END RESET } ]

 

I would only allow “ON TRANSACTION END RESET”.

I think we don’t need both here.

Philippe Beaudoin was indeed talking about the TRANSACTIONAL keyword, but that would have make sense (and I think that’s what he meant) , if you could do something like “CREATE [NON] TRANSACTIONAL VARIABLE …”.

But here I don’t think that the ON TRANSACTIONAL END RESET has any sense in English, and it only complicates the syntax.

 

Maybe Thomas Vondra (if it’s him) would be more inclined to commit the patch if it has this more simple syntax has he requested.

 

What do you think ?


I removed TRANSACTIONAL from this clause, see attachement change.diff

Updated patch attached.

I hope it would be the last touch, making it fully ready for a commiter.


Thank you very much for review and testing

documentation fix



Pavel
Attachment

pgsql-hackers by date:

Previous
From: Pavel Stehule
Date:
Subject: Re: proposal: schema variables
Next
From: Justin Pryzby
Date:
Subject: Re: explain HashAggregate to report bucket and memory stats