| From: | Michael Paquier <michael(dot)paquier(at)gmail(dot)com> |
|---|---|
| To: | PostgreSQL mailing lists <pgsql-hackers(at)postgresql(dot)org> |
| Cc: | Stephen Frost <sfrost(at)snowman(dot)net> |
| Subject: | Improving regression tests to check LOCK TABLE and table permissions |
| Date: | 2015-05-12 02:52:00 |
| Message-ID: | CAB7nPqTpdh3ZwYdqEMEo5HW_6nwvud1iVTOHrHKotu0X1r4_bQ@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hi all,
As mentioned in this thread, it would be good to have regression tests
to test the interactions with permissions and LOCK TABLE:
http://www.postgresql.org/message-id/[email protected]
Attached is a patch achieving that.
Note that it does some checks on the modes SHARE ACCESS, ROW EXCLUSIVE
and ACCESS EXCLUSIVE to check all the code paths of
LockTableAclCheck(at)lockcmds(dot)c(dot)
I'll add an entry in the next CF to keep track of it.
Regards,
--
Michael
| Attachment | Content-Type | Size |
|---|---|---|
| 20150512_lock_table_privileges.patch | text/x-diff | 5.5 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Etsuro Fujita | 2015-05-12 02:53:38 | Re: EvalPlanQual behaves oddly for FDW queries involving system columns |
| Previous Message | Michael Paquier | 2015-05-12 02:46:38 | Re: LOCK TABLE Permissions |