| From: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
|---|---|
| To: | Heikki Linnakangas <hlinnaka(at)iki(dot)fi> |
| Cc: | Dennis Bjorklund <db(at)zigo(dot)dhs(dot)org>, pgsql-patches(at)postgresql(dot)org |
| Subject: | Re: lastval() |
| Date: | 2005-05-10 21:34:18 |
| Message-ID: | 428128DA.1050101@dunslane.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-patches |
Heikki Linnakangas wrote:
> On Mon, 9 May 2005, Dennis Bjorklund wrote:
>
>> The thing is that I don't care how it's implemented, it's the feature
>> itself that is more importent to decide if we want it or not. I'm
>> sure the
>> code can be fixed so everybody is happy it in the end,
>
>
> You could implement this on top of the current nextval without backend
> changes.
>
> Create a wrapper function on top of nextval that stores the value in a
> temp table. Or a session variable if your PL language of choice has them.
>
> lastval would do a select on the temp table.
>
>
And this is making life easier for anybody? I don't think so.
cheers
andrew
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Simon Riggs | 2005-05-10 21:46:05 | Re: Cost of XLogInsert CRC calculations |
| Previous Message | Heikki Linnakangas | 2005-05-10 21:23:45 | Re: lastval() |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2005-05-10 22:28:19 | Re: [PATCHES] Cleaning up unreferenced table files |
| Previous Message | Heikki Linnakangas | 2005-05-10 21:23:45 | Re: lastval() |