Re: Running the fdw test from the terminal crashes into the core-dump
Tom Lane <tgl@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Alvaro Herrera <alvherre@alvh.no-ip.org>
Cc: Alena Rybakina <a.rybakina@postgrespro.ru>,
Pgsql Hackers <pgsql-hackers@postgresql.org>,
Amit Langote <amitlangote09@gmail.com>
Date: 2024-02-22T23:48:20Z
Lists: pgsql-hackers
Attachments
- merge-privilege-doc.patch (text/x-diff) patch
Alvaro Herrera <alvherre@alvh.no-ip.org> writes:
> After having pushed that, I wonder if we should document this. It seems
> quite the minor thing, but I'm sure somebody will complain if we don't.
Yup, no doubt.
> I propose the attached. (Extra context so that the full paragraph can
> be read from the comfort of your email program.)
This reads awkwardly to me. I think it'd be better to construct it
so that DO NOTHING's requirement is stated exactly parallel to the other
three clause types, more or less as attached.
> (While at it, I found the placement of the previous-to-last sentence in
> that paragraph rather strange, so I moved it to the end.)
Agreed, and done in my version too.
BTW, if you read it without paying attention to markup, you'll notice
that we are saying things like
If you specify an insert action, you must have the INSERT
privilege on the target_table_name.
which is fairly nonsensical: we don't define privileges on the name
of something. While I've not done anything about that here,
I wonder if we shouldn't just write "privilege on the target table"
without any special markup.
regards, tom lane
Commits
-
Revise MERGE documentation
- c4bd6ff57c9a 16.3 landed
- 6979ea2638a5 17.0 landed
- 172d7f7e666e 15.7 landed
-
MERGE ... DO NOTHING: require SELECT privileges
- a3f5d2056ceb 16.3 landed
- 90ad85db6a4e 15.7 landed
- 4989ce72644b 17.0 landed
-
Rework query relation permission checking
- a61b1f74823c 16.0 cited