Re: Largeobject Access Controls and pg_migrator

From: Bruce Momjian <bruce(at)momjian(dot)us>
To: Takahiro Itagaki <itagaki(dot)takahiro(at)oss(dot)ntt(dot)co(dot)jp>
Cc: KaiGai Kohei <kaigai(at)kaigai(dot)gr(dot)jp>, KaiGai Kohei <kaigai(at)ak(dot)jp(dot)nec(dot)com>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Largeobject Access Controls and pg_migrator
Date: 2009-12-16 22:20:33
Message-ID: 200912162220.nBGMKXQ02771@momjian.us
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Takahiro Itagaki wrote:
>
> KaiGai Kohei <kaigai(at)kaigai(dot)gr(dot)jp> wrote:
>
> > Can SELECT lo_create(16385); help this situation?
>
> SELECT lo_create(loid) FROM (SELECT DISTINCT loid FROM pg_largeobject) AS t
>
> would work for pg_migrator.
>
> > I'm not clear whether we also check pg_largeobejct has chunks with same
> > LOID on lo_create(). In the regular operation, it shall never happen.
>
> I think the omission is a reasonable optimization.

Thanks, I have updated pg_migrator to use your suggested method.

--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com

+ If your life is a hard drive, Christ can be your backup. +

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Jeff Davis 2009-12-16 22:25:24 Re: Range types
Previous Message Kevin Grittner 2009-12-16 22:18:41 determine snapshot after obtaining locks for first statement