Re: Select for update

Bruno,

I know this is inefficient. In fact it was someone other's problem to
eliminate gaps and I solved it this way. I don't do such things for myself.

Best Regards,
Otto

----- Original Message -----
From: "Bruno Wolff III" <bruno(at)wolff(dot)to>
To: "Havasvölgyi Ottó" <h(dot)otto(at)freemail(dot)hu>
Cc: <pgsql-general(at)postgresql(dot)org>
Sent: Friday, July 29, 2005 8:58 AM
Subject: Re: [GENERAL] Select for update

> On Fri, Jul 29, 2005 at 00:05:46 +0200,
> Havasvölgyi Ottó <h(dot)otto(at)freemail(dot)hu> wrote:
>>
>> This function deletes a row, and updates the pid field where pid is
>> geater
>> than the deleted pid value, so that the gap caused by the deletion is not
>> present any more.
>
> This isn't directly related to your problem, but why are you doing this?
> This is a pretty inefficient thing to be doing unless there is a business
> rule that there can't be gaps in the pid values. If you just want to
> number rows in reports, you should do that in your reporting application,
> not by continuously renumbering your records.
>
> ---------------------------(end of broadcast)---------------------------
> TIP 5: don't forget to increase your free space map settings
>
>