From: | Andrew Gierth <andrew(at)tao11(dot)riddles(dot)org(dot)uk> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Adam Brightwell <adam(dot)brightwell(at)crunchydata(dot)com>, Paul Ramsey <pramsey(at)cleverelephant(dot)ca>, pgsql-hackers(at)lists(dot)postgresql(dot)org, Peter Geoghegan <peter(dot)geoghegan(at)crunchydata(dot)com>, Joe Conway <joe(at)crunchydata(dot)com> |
Subject: | Re: Changing SQL Inlining Behaviour (or...?) |
Date: | 2019-01-20 00:41:32 |
Message-ID: | 871s586uri.fsf@news-spur.riddles.org.uk |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
>>>>> "Tom" == Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> writes:
Tom> The other thing we need to consider is whether we need any
Tom> documentation adjustments. I believe that right now, the rules for
Tom> inlining SQL functions are not documented anywhere but the code,
That is correct, though we got so tired of explaining it on IRC that
there is a wiki page (though it hasn't been updated since 9.5, but I'm
pretty sure there aren't any significant changes needed):
https://wiki.postgresql.org/wiki/Inlining_of_SQL_functions
--
Andrew (irc:RhodiumToad)
From | Date | Subject | |
---|---|---|---|
Next Message | Vik Fearing | 2019-01-20 01:11:19 | Re: pg_stat_statements vs. SELECT FOR UPDATE |
Previous Message | Paul Martinez | 2019-01-20 00:40:40 | [PROPOSAL] ON DELETE SET NULL (<column_list>) for Foreign Key Constraints |