Re: [HACKERS] SQL procedures
От
Peter Eisentraut
Тема
Re: [HACKERS] SQL procedures
Дата
Msg-id
492a8be0-ff55-3858-7dc1-62fa07d444c2@2ndquadrant.com
Ответ на
Re: [HACKERS] SQL procedures (Simon Riggs)
Список
Дерево обсуждения
[HACKERS] SQL procedures Peter Eisentraut <peter.eisentraut@2ndquadrant.com>
Re: [HACKERS] SQL procedures Tom Lane <tgl@sss.pgh.pa.us>
Re: [HACKERS] SQL procedures Peter Eisentraut <peter.eisentraut@2ndquadrant.com>
Re: [HACKERS] SQL procedures Tom Lane <tgl@sss.pgh.pa.us>
Re: [HACKERS] SQL procedures Peter Eisentraut <peter.eisentraut@2ndquadrant.com>
Re: [HACKERS] SQL procedures Tom Lane <tgl@sss.pgh.pa.us>
Re: [HACKERS] SQL procedures Peter Eisentraut <peter.eisentraut@2ndquadrant.com>
Re: [HACKERS] SQL procedures Tom Lane <tgl@sss.pgh.pa.us>
Re: [HACKERS] SQL procedures "Daniel Verite" <daniel@manitou-mail.org>
Re: [HACKERS] SQL procedures Simon Riggs <simon@2ndquadrant.com>
Re: [HACKERS] SQL procedures Laurenz Albe <laurenz.albe@cybertec.at>
Re: [HACKERS] SQL procedures Pavel Stehule <pavel.stehule@gmail.com>
Re: [HACKERS] SQL procedures Robert Haas <robertmhaas@gmail.com>
Re: [HACKERS] SQL procedures Tom Lane <tgl@sss.pgh.pa.us>
Re: [HACKERS] SQL procedures Robert Haas <robertmhaas@gmail.com>
Re: [HACKERS] SQL procedures Andrew Dunstan <andrew.dunstan@2ndquadrant.com>
Re: [HACKERS] SQL procedures Robert Haas <robertmhaas@gmail.com>
Re: [HACKERS] SQL procedures Andrew Dunstan <andrew.dunstan@2ndquadrant.com>
Re: [HACKERS] SQL procedures Pavel Stehule <pavel.stehule@gmail.com>
Re: [HACKERS] SQL procedures Peter Eisentraut <peter.eisentraut@2ndquadrant.com>
Re: [HACKERS] SQL procedures Peter Eisentraut <peter.eisentraut@2ndquadrant.com>
prokind column (was Re: [HACKERS] SQL procedures) Peter Eisentraut <peter.eisentraut@2ndquadrant.com>
Re: prokind column (was Re: [HACKERS] SQL procedures) Tom Lane <tgl@sss.pgh.pa.us>
Re: prokind column (was Re: [HACKERS] SQL procedures) Peter Eisentraut <peter.eisentraut@2ndquadrant.com>
Re: prokind column (was Re: [HACKERS] SQL procedures) Tom Lane <tgl@sss.pgh.pa.us>
Re: prokind column (was Re: [HACKERS] SQL procedures) Michael Paquier <michael@paquier.xyz>
Re: prokind column (was Re: [HACKERS] SQL procedures) Tom Lane <tgl@sss.pgh.pa.us>
Re: prokind column (was Re: [HACKERS] SQL procedures) Peter Eisentraut <peter.eisentraut@2ndquadrant.com>
Re: prokind column (was Re: [HACKERS] SQL procedures) Michael Paquier <michael@paquier.xyz>
Re: prokind column (was Re: [HACKERS] SQL procedures) Peter Eisentraut <peter.eisentraut@2ndquadrant.com>
Re: prokind column (was Re: [HACKERS] SQL procedures) Catalin Iacob <iacobcatalin@gmail.com>
Re: prokind column (was Re: [HACKERS] SQL procedures) Tom Lane <tgl@sss.pgh.pa.us>
Re: prokind column (was Re: [HACKERS] SQL procedures) Michael Paquier <michael@paquier.xyz>
Re: prokind column (was Re: [HACKERS] SQL procedures) John Naylor <jcnaylor@gmail.com>
Re: [HACKERS] SQL procedures Pavel Stehule <pavel.stehule@gmail.com>
Re: [HACKERS] SQL procedures Pavel Stehule <pavel.stehule@gmail.com>
Re: [HACKERS] SQL procedures Peter Eisentraut <peter.eisentraut@2ndquadrant.com>
Re: [HACKERS] SQL procedures Pavel Stehule <pavel.stehule@gmail.com>
Re: [HACKERS] SQL procedures Pavel Stehule <pavel.stehule@gmail.com>
Re: [HACKERS] SQL procedures Peter Eisentraut <peter.eisentraut@2ndquadrant.com>
Re: [HACKERS] SQL procedures Merlin Moncure <mmoncure@gmail.com>
Re: [HACKERS] SQL procedures Peter Eisentraut <peter.eisentraut@2ndquadrant.com>
Re: [HACKERS] SQL procedures Merlin Moncure <mmoncure@gmail.com>
Re: [HACKERS] SQL procedures Peter Eisentraut <peter.eisentraut@2ndquadrant.com>
Re: [HACKERS] SQL procedures Merlin Moncure <mmoncure@gmail.com>
Re: [HACKERS] SQL procedures Peter Eisentraut <peter.eisentraut@2ndquadrant.com>
Re: [HACKERS] SQL procedures Konstantin Knizhnik <k.knizhnik@postgrespro.ru>
Re: [HACKERS] SQL procedures Simon Riggs <simon@2ndquadrant.com>
Re: [HACKERS] SQL procedures Simon Riggs <simon@2ndquadrant.com>
Re: [HACKERS] SQL procedures Peter Eisentraut <peter.eisentraut@2ndquadrant.com>
Re: [HACKERS] SQL procedures Peter Eisentraut <peter.eisentraut@2ndquadrant.com>
Re: [HACKERS] SQL procedures Andrew Dunstan <andrew.dunstan@2ndquadrant.com>
Re: [HACKERS] SQL procedures Peter Eisentraut <peter.eisentraut@2ndquadrant.com>
Re: [HACKERS] SQL procedures Tom Lane <tgl@sss.pgh.pa.us>
Re: [HACKERS] SQL procedures Andrew Dunstan <andrew.dunstan@2ndquadrant.com>
Re: [HACKERS] SQL procedures Peter Eisentraut <peter.eisentraut@2ndquadrant.com>
Re: [HACKERS] SQL procedures Andrew Dunstan <andrew.dunstan@2ndquadrant.com>
Re: [HACKERS] SQL procedures Peter Eisentraut <peter.eisentraut@2ndquadrant.com>
Re: [HACKERS] SQL procedures Thomas Munro <thomas.munro@enterprisedb.com>
Re: [HACKERS] SQL procedures Peter Eisentraut <peter.eisentraut@2ndquadrant.com>
Re: [HACKERS] SQL procedures Robert Haas <robertmhaas@gmail.com>
Re: [HACKERS] SQL procedures Simon Riggs <simon@2ndquadrant.com>
Re: [HACKERS] SQL procedures Simon Riggs <simon@2ndquadrant.com>
Re: [HACKERS] SQL procedures Peter Eisentraut <peter.eisentraut@2ndquadrant.com>
Re: [HACKERS] SQL procedures Pavel Stehule <pavel.stehule@gmail.com>
Re: [HACKERS] SQL procedures Corey Huinker <corey.huinker@gmail.com>
Re: [HACKERS] SQL procedures Andrew Dunstan <andrew.dunstan@2ndquadrant.com>
Re: [HACKERS] SQL procedures Craig Ringer <craig@2ndquadrant.com>
Re: [HACKERS] SQL procedures Peter Eisentraut <peter.eisentraut@2ndquadrant.com>
Re: [HACKERS] SQL procedures Andrew Dunstan <andrew.dunstan@2ndquadrant.com>
On 11/6/17 16:27, Simon Riggs wrote: > You mention PARALLEL SAFE is not used for procedures. Isn't it an > architectural restriction that procedures would not be able to execute > in parallel? (At least this year) I'm not sure what you are referring to here. I don't think the functionality I'm proposing does anything in parallel or has any interaction with it. > I think we need an explanatory section of the docs, but there doesn't > seem to be one for Functions, so there is no place to add some text > that says the above. > > I found it confusing that ALTER and DROP ROUTINE exists but not CREATE > ROUTINE. At very least we should say somewhere "there is no CREATE > ROUTINE", so its absence is clearly intentional. I did wonder whether > we should have it as well, but its just one less thing to review, so > good. I'll look for a place to add some documentation around this. > Was surprised that pg_dump didn't use DROP ROUTINE, when appropriate. It's not clear to me why that would be preferred. -- Peter Eisentraut http://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
В списке pgsql-hackers по дате отправления