| From: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
|---|---|
| To: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Typo in online docs |
| Date: | 2010-02-24 14:12:09 |
| Message-ID: | 20100224141209.GE3790@alvh.no-ip.org |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
strk wrote:
> On this page:
> http://www.postgresql.org/docs/8.4/interactive/explicit-locking.html
>
> This chapter:
> 13.3.4. Advisory Locks
>
> This example:
> SELECT pg_advisory_lock(id) FROM foo WHERE id = 12345; -- ok
> SELECT pg_advisory_lock(id) FROM foo WHERE id > 12345 LIMIT 100; -- danger!
> SELECT pg_advisory_lock(q.id) FROM
> (
> SELECT id FROM foo WHERE id > 12345 LIMIT 100;
> ) q; -- ok
>
> Last statement seems bogus to me ...
Removed semicolon, thanks for the report
--
Alvaro Herrera http://www.CommandPrompt.com/
PostgreSQL Replication, Consulting, Custom Development, 24x7 support
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Gokulakannan Somasundaram | 2010-02-24 14:41:00 | Re: A thought on Index Organized Tables |
| Previous Message | Dave Page | 2010-02-24 13:50:54 | Re: FW: Unable to install PostgreSQL on Windows Server 2003 SP2 |