I realize 7.2.4 is long in the tooth, but it's an old system that's been
running for several years now. Someday we'll upgrade...
However, part of the upgrade will involve dumping and restoring the
tables. I've just did a little playing with pg_dump on one of
the databases and discovered that I
Steve Wampler [EMAIL PROTECTED] writes:
-gunzip atst.logdb.out.gz | psql -q
ERROR: permission denied to set session authorization
ERROR: permission denied for language c
ERROR: must be superuser to create procedural language
I see all the permission denied messages, but why? How can a
Steve Wampler wrote:
I realize 7.2.4 is long in the tooth, but it's an old system that's been
running for several years now. Someday we'll upgrade...
However, part of the upgrade will involve dumping and restoring the
tables. I've just did a little playing with pg_dump on one of
the databases
On Mon, Jan 31, 2005 at 09:45:16 -0700,
Steve Wampler [EMAIL PROTECTED] wrote:
Steve Wampler wrote:
I realize 7.2.4 is long in the tooth, but it's an old system that's been
running for several years now. Someday we'll upgrade...
There are more recent releases even within the 7.2.x series.
Tom Lane wrote:
Steve Wampler [EMAIL PROTECTED] writes:
-gunzip atst.logdb.out.gz | psql -q
ERROR: permission denied to set session authorization
ERROR: permission denied for language c
ERROR: must be superuser to create procedural language
I see all the permission denied messages, but why?
Steve Wampler [EMAIL PROTECTED] writes:
In fact, now that I look more at the dump file, it's kinda interesting.
Near the top are the lines:
\connect atst.logdb atst
SET client_encoding = 'SQL_ASCII';
SET check_function_bodies = false;
SET SESSION AUTHORIZATION 'sbw';
