Re: Complexity of contrib types - Mailing list pgsql-hackers

From Hannu Krosing
Subject Re: Complexity of contrib types
Date
Msg-id 35B4BBA0.44E66103@trust.ee
Whole thread Raw
In response to Re: Complexity of contrib types  (Bruce Momjian <maillist@candle.pha.pa.us>)
Responses Re: Complexity of contrib types
List pgsql-hackers
Bruce Momjian wrote:
>
>
> We could create a function that returned the previously inserted oid,
> and use that in the next query.
>
>         insert into test values (4);
>         update test3 set val = lastoid();
>
> Just remember the lastoid inserted in the backend code.  Seems easy.  Do
> you want it added to the TODO list.

Yes. It could be used in several places.

But I'm currently not aware about the future of oid's 'at the large'.

I have understood that we are on a way of getting rid of OIDs for
non-system tables (and having to re-implement them using triggers
and sequences where/when needed)?

Hannu

pgsql-hackers by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: Complexity of contrib types
Next
From: darcy@druid.net (D'Arcy J.M. Cain)
Date:
Subject: Re: [HACKERS] cidr