From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
---|---|
To: | Bruce Momjian <bruce(at)momjian(dot)us> |
Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: What is lo_insert? |
Date: | 2011-01-06 02:20:34 |
Message-ID: | AANLkTik0YcgjvHPm3eoi7Uax3CoO9h3t4uEOc+5yskaY@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Wed, Jan 5, 2011 at 12:21 PM, Bruce Momjian <bruce(at)momjian(dot)us> wrote:
> The psql manual page mentions lo_insert:
>
> LASTOID
> The value of the last affected OID, as returned
> --> from an INSERT or lo_insert command. This variable
> is only guaranteed to be valid until after the
> result of the next SQL command has been displayed.
>
> Should that be lo_import? I don't see lo_insert used anywhere. And it
> doesn't seem lo_import sets LASTOID.
I think it's supposed to be lo_import. It sets LASTOID if you do this:
rhaas=# \lo_import '/etc/passwd'
lo_import 16414
rhaas=# select :LASTOID;
?column?
----------
16414
(1 row)
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2011-01-06 02:28:23 | Fix for pg_upgrade migrating pg_largeobject_metadata |
Previous Message | Robert Haas | 2011-01-06 02:10:15 | Re: crash-safe visibility map, take three |