In 7.1 and current sources, trying to use initdb's --sysid option to set
the postgres superuser's sysid does not work correctly. pg_shadow is
set up with the correct username and usesysid, but about half of the
standard system objects are nonetheless created with the postgres user's
Unix sysid.
"Alexander Zagrebin" <[EMAIL PROTECTED]> writes:
> But if "rec" is declared as "hierarchy%ROWTYPE", then
> execution fails with such log messages:
I can't duplicate this in current sources. Please try 7.1.2.
regards, tom lane
---(end of broadcast
> 1. index_getprocid (backend/access/index/idexam.c) doesn't
>properly supports multi-keys indexes with procnum > 1
>it's works only if either procnum=1 (B-tree, hash) or attnum=1
It looks to me like IndexSupportInitialize and index_getprocid have
different ideas about whether procnum or
"karthikeyan V" <[EMAIL PROTECTED]> writes:
> "failed sanity check, table user_details was not found
> pg_dump failed on users, exiting"
Probably, you deleted the pg_shadow entry for the user that owned this
table. 7.1's pg_dump is somewhat smarter about this sort of situation,
but in older vers
Ondrej Palkovsky <[EMAIL PROTECTED]> writes:
> I have the following function. When the function is executed and it gets
> to the 'IF NOT FOUND', the backend gets restarted.
Is this in 7.1.1? There's an embarrassing bug in 7.1.1 --- plpgsql
coredumps on a SELECT that returns no rows. It's fixed
Bruce Momjian <[EMAIL PROTECTED]> writes:
>> (Hey Marc, where is 7.1.2 anyway?)
> We were waiting on some optimizer change, I thought. I don't remember
> the specifics but I thought it had to do with UNION plans.
No such issue pending that I know of.
regards, tom lane
