| From: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
|---|---|
| To: | Heikki Linnakangas <hlinnakangas(at)vmware(dot)com> |
| Cc: | Josh Berkus <josh(at)agliodbs(dot)com>, Kevin Grittner <kgrittn(at)ymail(dot)com>, Peter Eisentraut <peter_e(at)gmx(dot)net>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: [PATCH] SQL assertions prototype |
| Date: | 2013-12-18 14:03:20 |
| Message-ID: | 52B1AB28.20002@dunslane.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 12/18/2013 06:00 AM, Heikki Linnakangas wrote:
>
>
> If you don't force everything to run in SSI mode, then you have to
> somehow figure out what parts do need to run in SSI mode to enforce
> the assertion. For example, if the assertion refers tables A and B,
> perhaps you can get away without predicate locks on table C?
>
>
But the assertion might simply run a function. For non-trivial cases
that's what I would expect people to do.
cheers
andrew
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Serge Negodyuck | 2013-12-18 14:20:48 | Re: BUG #8673: Could not open file "pg_multixact/members/xxxx" on slave during hot_standby |
| Previous Message | Andrew Dunstan | 2013-12-18 14:00:40 | Re: ALTER SYSTEM SET command to change postgresql.conf parameters |