Thanks Tom.
Yes, I am on 6.4. As to gdb, I really wouldn't know how to get the info you
request. The segfault doesn't result in a core file either.
There is nothing sacred about my project (supporting RADIUS authentication),
I'll happily send you my database creation scripts if you want to try making
this happen yourself. This is 6.4 as stated, running on a SuSE 5.3 (Linux
2.0.34) distribution. No problems running the database and all the build
tests work fine.
I have no permissions attached to triggers as far as I know; and the
permissions aren't complicated either. The segfault occurs when running the
dump as user postgres, which should have godlike permissions anyway...
Regards, K.
Am 24-Nov-98 schrieb Tom Lane:
> Karl Auer <auer@kom.id.ethz.ch> writes:
>> When I use the "-z" option (dump permissions)when dumping a database I
>> have, I get a segfault and no output.
>
> Are you on Postgres 6.4? I recall fixing several nasty problems with
> permissions in pg_dump between 6.3.2 and 6.4.
>
> If you are on 6.4, could you use gdb or something to get a backtrace
> showing exactly where pg_dump dies?
---
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Karl Auer (auer@kom.id.ethz.ch) Geschaeft/work +41-1-6327531
Kommunikation, ETHZ RZ Privat/home +41-1-4517941
Clausiusstrasse 59 Fax +41-1-6321225
CH-8092 ZUERICH Switzerland
