pg.ddx.io pgsql-admin@postgresql.org mailing list archive
help / color / mirror / Atom feedPermission denied: LOCK TABLE test.__proc IN ACCESS SHARE MODE
3+ messages / 3 participants
[nested] [flat]
* Permission denied: LOCK TABLE test.__proc IN ACCESS SHARE MODE
@ 2006-05-06 01:44 kynn@panix.com
2006-05-06 01:57 ` Re: Permission denied: LOCK TABLE test.__proc IN ACCESS SHARE MODE Alvaro Herrera <alvherre@commandprompt.com>
2006-05-06 02:08 ` Re: Permission denied: LOCK TABLE test.__proc IN ACCESS SHARE MODE Tom Lane <tgl@sss.pgh.pa.us>
0 siblings, 2 replies; 3+ messages in thread
From: kynn@panix.com @ 2006-05-06 01:44 UTC (permalink / raw)
To: pgsql-admin
When I run pg_dump I get this error:
pg_dump: SQL command failed
pg_dump: Error message from server: ERROR: permission denied for schema test
pg_dump: The command was: LOCK TABLE test.__proc IN ACCESS SHARE MODE
I can't find out what transaction is responsible for this lock. When
I look at the pg_locks table, I see only two locks, and they both seem
to be due to the fact that I am interacting with psql at the moment,
and this interaction is in no way directed to the database I'm trying
to dump.
Is there a way for me to find out the transaction responsible for the
lock that's causing the error message? If so, how can I kill this
transaction?
kj
^ permalink raw reply [nested|flat] 3+ messages in thread
* Re: Permission denied: LOCK TABLE test.__proc IN ACCESS SHARE MODE
2006-05-06 01:44 Permission denied: LOCK TABLE test.__proc IN ACCESS SHARE MODE kynn@panix.com
@ 2006-05-06 01:57 ` Alvaro Herrera <alvherre@commandprompt.com>
1 sibling, 0 replies; 3+ messages in thread
From: Alvaro Herrera @ 2006-05-06 01:57 UTC (permalink / raw)
To: kynn@panix.com; +Cc: pgsql-admin
kynn@panix.com wrote:
> pg_dump: SQL command failed
> pg_dump: Error message from server: ERROR: permission denied for schema test
> pg_dump: The command was: LOCK TABLE test.__proc IN ACCESS SHARE MODE
>
> I can't find out what transaction is responsible for this lock. When
> I look at the pg_locks table, I see only two locks, and they both seem
> to be due to the fact that I am interacting with psql at the moment,
> and this interaction is in no way directed to the database I'm trying
> to dump.
You are assuming that the problem is that there is a lock conflict.
This is not the case; you'd not get an error message (unless the command
had specified NOWAIT).
The problem here seems to be that you are trying to dump a schema or
table that the dumping user has no access to. You may either grant
those permissions, or create the dump with another user.
--
Alvaro Herrera http://www.CommandPrompt.com/
PostgreSQL Replication, Consulting, Custom Development, 24x7 support
^ permalink raw reply [nested|flat] 3+ messages in thread
* Re: Permission denied: LOCK TABLE test.__proc IN ACCESS SHARE MODE
2006-05-06 01:44 Permission denied: LOCK TABLE test.__proc IN ACCESS SHARE MODE kynn@panix.com
@ 2006-05-06 02:08 ` Tom Lane <tgl@sss.pgh.pa.us>
1 sibling, 0 replies; 3+ messages in thread
From: Tom Lane @ 2006-05-06 02:08 UTC (permalink / raw)
To: kynn@panix.com; +Cc: pgsql-admin
<kynn@panix.com> writes:
> When I run pg_dump I get this error:
> pg_dump: SQL command failed
> pg_dump: Error message from server: ERROR: permission denied for schema test
> pg_dump: The command was: LOCK TABLE test.__proc IN ACCESS SHARE MODE
> I can't find out what transaction is responsible for this lock.
What lock? The error is "permission denied". It looks like whatever
user you're running pg_dump as doesn't have USAGE permission on that
schema.
regards, tom lane
^ permalink raw reply [nested|flat] 3+ messages in thread
end of thread, other threads:[~2006-05-06 02:08 UTC | newest]
Thread overview: 3+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2006-05-06 01:44 Permission denied: LOCK TABLE test.__proc IN ACCESS SHARE MODE kynn@panix.com
2006-05-06 01:57 ` Alvaro Herrera <alvherre@commandprompt.com>
2006-05-06 02:08 ` Tom Lane <tgl@sss.pgh.pa.us>
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox