| From: | Martín Marqués <martin(dot)marques(at)gmail(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | pgsql-general <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: pg_lock_status not documented |
| Date: | 2011-09-02 22:40:53 |
| Message-ID: | CABeG9LtitrWTDQw-=LiF5Ca3hCyMgWpNbSH3+RE5Cd-8YPgDEA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
I know pg_locks, but I thought maybe pg_lock_status had some extra info.
Thanks anyway
2011/9/2 Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>:
> =?UTF-8?B?TWFydMOtbiBNYXJxdcOpcw==?= <martin(dot)marques(at)gmail(dot)com> writes:
>> I'm searching for information on pg_lock_status() function, but there
>> seams to be nothing in the docs. Maybe missing?
>
> It's not documented because it's an internal function that you shouldn't
> call directly. Look at the docs for the pg_locks view, which is the
> public API.
>
> regards, tom lane
>
--
Martín Marqués
select 'martin.marques' || '@' || 'gmail.com'
DBA, Programador, Administrador
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Josh Berkus | 2011-09-02 23:48:45 | Looking for an intro-to-SQL book which is PostgreSQL-friendly |
| Previous Message | Scott Ribe | 2011-09-02 20:51:52 | Re: Variable column name |