Skip site navigation (1) Skip section navigation (2)

Re: [HACKERS] pg_dump - segfault with -z option

From: Bruce Momjian <maillist(at)candle(dot)pha(dot)pa(dot)us>
To: auer(at)kom(dot)id(dot)ethz(dot)ch
Cc: pgsql-hackers(at)postgreSQL(dot)org
Subject: Re: [HACKERS] pg_dump - segfault with -z option
Date: 1998-11-24 16:08:42
Message-ID: 199811241608.LAA04238@candle.pha.pa.us (view raw or flat)
Thread:
Lists: pgsql-hackers
[Charset iso-8859-1 unsupported, filtering to ASCII...]
> hi.
> 
> I hope this is not a rehash of anything; a quick look at the mailing list
> archives turned up similar, but not identical stories.
> 
> When I use the "-z" option (dump permissions)when dumping a database I have, I
> get a segfault and no output. The other options are irrelevant (i.e., I can
> specify any other option or options I like, it still happens). To the best of
> my knowledge I have nothing tricky or complex in my database, just standard
> types like varchar, bool and int, the refint stuff and a trigger or two.
> 
> It does NOT segfault with template1, but nor do I get any output, maybe this
> is normal, I'm a total novice at this  :-)
> 
> This is not a critical issue for me, I can always set the permissions on my
> tables manually, but a) it would be nice not to have to and b) I thought it
> might interest someone... Seems to me that whatever the reasons for it,
> pg_dump should not lose it to the extent of segfaulting :-)

I believe this will be fixed in the first 6.4 minor release.  Should we
schedule 6.4.1 soon, folks.

-- 
  Bruce Momjian                        |  http://www.op.net/~candle
  maillist(at)candle(dot)pha(dot)pa(dot)us            |  (610) 853-3000
  +  If your life is a hard drive,     |  830 Blythe Avenue
  +  Christ can be your backup.        |  Drexel Hill, Pennsylvania 19026

In response to

Responses

pgsql-hackers by date

Next:From: Tom LaneDate: 1998-11-24 16:17:58
Subject: Re: [HACKERS] Parser bug?
Previous:From: Jan WieckDate: 1998-11-24 16:07:06
Subject: Re: [SQL] MINUS and slow 'not in'

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group