| From: | rob stone <floriparob(at)gmail(dot)com> |
|---|---|
| To: | Christophe Pettus <xof(at)thebuild(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Bill Moran <wmoran(at)potentialtech(dot)com>, pgsql-general list <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: AccessExclusiveLock on tuple? |
| Date: | 2015-12-02 20:06:58 |
| Message-ID: | 1449086818.5806.44.camel@gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Wed, 2015-12-02 at 10:47 -0800, Christophe Pettus wrote:
> On Dec 2, 2015, at 10:29 AM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> > The short answer is that heavyweight tuple locks can be taken
> > internally
> > by UPDATE, DELETE, and other row-level operations, and the
> > specifics of
> > which type of lock any given action takes are implementation
> > details that
> > can change from time to time.
>
> Great, thank you!
>
> --
> -- Christophe Pettus
> xof(at)thebuild(dot)com
>
>
>
Don't know if this helps at all. On the hot standby doco.
http://www.postgresql.org/docs/9.4/static/hot-standby.html
About two-thirds of the way down it refers to the pg_locks table.
Are you using "hot standby"?
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jim Nasby | 2015-12-02 22:43:53 | Re: full_page_writes on SSD? |
| Previous Message | David Steele | 2015-12-02 19:56:53 | Re: Pgbasebackup help |