I have very simple database without triggers and also see
20:10[mira]:~/tmp>pg_dump -z guta > qq
Segmentation fault
Database = guta+---------------------+----------------------------------------+| Relation | Grant/Revoke
Permissions |+---------------------+----------------------------------------+| groups |
{"=","megera=arwR","er=r","httpd=arw"}|| groups_pkey | || status
| {"=","megera=arwR","er=r","httpd=arw"} || status_pkey | ||
stidx_status_id | || ugmidx_group_id |
|| ugmidx_user_id | || user_group_map |
{"=","megera=arwR","er=r","httpd=arw"}|| user_group_map_pkey | || users
| {"=","megera=arwR","er=r","httpd=arw"} || users_pkey | ||
Regards,
Oleg
On Tue, 24 Nov 1998, Tom Lane wrote:
> Date: Tue, 24 Nov 1998 11:25:46 -0500
> From: Tom Lane <tgl@sss.pgh.pa.us>
> To: auer@kom.id.ethz.ch
> Cc: pgsql-hackers@postgreSQL.org
> Subject: Re: [HACKERS] pg_dump - segfault with -z option
>
> 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?
>
> FWIW, I currently use -z routinely, but my database is probably even
> simpler than yours ... no triggers, for example. My guess is pg_dump
> doesn't work for permissions attached to a trigger, or something along
> that line.
>
> regards, tom lane
>
_____________________________________________________________
Oleg Bartunov, sci.researcher, hostmaster of AstroNet,
Sternberg Astronomical Institute, Moscow University (Russia)
Internet: oleg@sai.msu.su, http://www.sai.msu.su/~megera/
phone: +007(095)939-16-83, +007(095)939-23-83