| From: | Simon Riggs <simon(at)2ndQuadrant(dot)com> |
|---|---|
| To: | Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com> |
| Cc: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Block level concurrency during recovery |
| Date: | 2008-10-23 17:32:06 |
| Message-ID: | 1224783126.27145.658.camel@ebony.2ndQuadrant |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Thu, 2008-10-23 at 20:24 +0300, Heikki Linnakangas wrote:
> Simon Riggs wrote:
> > On Thu, 2008-10-23 at 19:21 +0300, Heikki Linnakangas wrote:
> >> You have other issues with those still, namely that
> >> table locks are not yet taken appropriately, so I'm not sure if this is
> >> worth worrying about until that's done.
> >
> > Please explain. If you know of a correctness issue, please say.
>
> Things like DROP TABLE need to take an AccessExclusiveLock, and you
> don't have that yet, no?
Oh right, I thought you meant something not already in the plan.
--
Simon Riggs www.2ndQuadrant.com
PostgreSQL Training, Services and Support
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Simon Riggs | 2008-10-23 18:37:35 | Re: Re: [COMMITTERS] pgsql: Rework subtransaction commit protocol for hot standby. |
| Previous Message | Josh Berkus | 2008-10-23 17:26:36 | Re: psql Feature request \set query |