Re: Select for update
От | Havasvölgyi Ottó |
---|---|
Тема | Re: Select for update |
Дата | |
Msg-id | 008f01c5942b$cc9b94e0$b800a8c0@OTTO обсуждение исходный текст |
Ответ на | Rules vs Triggers (Randall Perry <rgp@systame.com>) |
Список | pgsql-general |
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@wolff.to> To: "Havasvölgyi Ottó" <h.otto@freemail.hu> Cc: <pgsql-general@postgresql.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.otto@freemail.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 > >
В списке pgsql-general по дате отправления: