| From: | Euler Taveira de Oliveira <euler(at)timbira(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Laerson Keler <laerson(dot)keler(at)lkmc(dot)com(dot)br>, pgsql-bugs(at)postgresql(dot)org |
| Subject: | Re: BUG #6258: Lock Sequence |
| Date: | 2011-10-17 19:13:13 |
| Message-ID: | 4E9C7E49.7040507@timbira.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On 17-10-2011 12:52, Tom Lane wrote:
> "Laerson Keler"<laerson(dot)keler(at)lkmc(dot)com(dot)br> writes:
>> Dear Srs, good morning, I did the automatic update postgresql 8.4.9 and
>> a function stopped working, I used the option select for update
>> in a sequence and is now giving the following error "can not lock rows in
>> sequence ...", how can I enable the blocking of the sequence?
>
You can't. It was disabled [1].
> Why did you do that, that is what were you trying to accomplish? It
> never did block nextval() on the sequence, for example.
>
Maybe he is using an old pgpool-II version?
--
Euler Taveira de Oliveira - Timbira http://www.timbira.com.br/
PostgreSQL: Consultoria, Desenvolvimento, Suporte 24x7 e Treinamento
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2011-10-17 19:43:09 | Re: BUG #6258: Lock Sequence |
| Previous Message | Laerson keler | 2011-10-17 18:03:54 | Re: BUG #6258: Lock Sequence |