Re: pg_largeobject implementation question

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Scott Corscadden <scott(at)corscadden(dot)ca>
Cc: "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>, "support(at)binnj(dot)com" <support(at)binnj(dot)com>
Subject: Re: pg_largeobject implementation question
Date: 2012-10-10 15:04:01
Message-ID: 27237.1349881441@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Scott Corscadden <scott(at)corscadden(dot)ca> writes:
> ** MY QUESTION ** - Will pg_largeobject automatically choose new OIDs that don't conflict, if I've added lo's this way, by direct COPY?

In 8.4, yes. In later versions, you'd need to do something about
creating corresponding rows in pg_largeobject_metadata.

In general, all built-in OID columns have mechanisms for choosing
nonconflicting new values --- but in 9.0 and up, pg_largeobject_metadata
is the authoritative store of "existing OIDs" for blobs, not
pg_largeobject.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Alvaro Herrera 2012-10-10 15:19:17 September 2012 commitfest
Previous Message Hannu Krosing 2012-10-10 15:03:54 Re: Is there a good reason why PL languages do not support cstring type arguments and return values ?