From: | Dmitriy Igrishin <dmitigr(at)gmail(dot)com> |
---|---|
To: | Vincent Veyron <vv(dot)lists(at)wanadoo(dot)fr> |
Cc: | Chris Travers <chris(dot)travers(at)gmail(dot)com>, Postgres General <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: How to create "auto-increment" field WITHOUT a sequence object? |
Date: | 2011-07-03 14:10:08 |
Message-ID: | CAAfz9KOKZVDQ1+thWEt+87ai2QEV6s4qgFG1ETHVt1mD6TM=ZA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Hey Vincent,
2011/7/3 Vincent Veyron <vv(dot)lists(at)wanadoo(dot)fr>
> Le vendredi 01 juillet 2011 à 12:28 +0400, Dmitriy Igrishin a écrit :
>
>
> > Then I don't clearly understand the existence of locks (the LOCK
> > command, SELECT FOR UPDATE clause and so on) if the usage
> > of them gives only problems...
> >
>
> Chris already explained why twice :
>
> "you MUST lock on insert to get gapless sequences"
>
Not me :-). The OP must do it. So, what problem here? Deadlocks?
Again, if deadlocks are so dangerous, why the LOCK command exists?
> Can't you just :
> -create the records with a regular sequence, that will have gaps
> -when you want to export, number an additional column from 1 to 10 000
> and use that as key
> ?
>
I don't use any locks explicitly :-)
> --
> Vincent Veyron
> http://marica.fr/
> Logiciel de gestion des sinistres et des contentieux pour le service
> juridique
>
>
--
// Dmitriy.
From | Date | Subject | |
---|---|---|---|
Next Message | Ireneusz Pluta | 2011-07-03 14:25:43 | Re: How to create "auto-increment" field WITHOUT a sequence object? |
Previous Message | Vincent Veyron | 2011-07-03 14:04:04 | Re: How to create "auto-increment" field WITHOUT a sequence object? |