BUG #1848: Segfault with pg_dump when database name omitted

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|

BUG #1848: Segfault with pg_dump when database name omitted

Eric Boutin

The following bug has been logged online:

Bug reference:      1848
Logged by:          Eric Boutin
Email address:      [hidden email]
PostgreSQL version: 8
Operating system:   Solaris 10 amd64
Description:        Segfault with pg_dump when database name omitted
Details:

Short example that tells it all :
[eric@imelda ~]$ pg_dump -U appserv -t tbl_dossiers -s
pg_dump: [archiver (db)] connection to database "Segmentation Fault (core
dumped)
[eric@imelda ~]$

It's not a major error in itself, but a segfault is never a good thing and
could potentially lead to buffer overflow/code execution

Fix : don't forget to append the database name

That's about it
Thanks for your good application

---------------------------(end of broadcast)---------------------------
TIP 2: Don't 'kill -9' the postmaster
Reply | Threaded
Open this post in threaded view
|

Re: BUG #1848: Segfault with pg_dump when database name omitted

Michael Fuhr
On Thu, Aug 25, 2005 at 07:41:59PM +0100, Eric Boutin wrote:
>
> [eric@imelda ~]$ pg_dump -U appserv -t tbl_dossiers -s
> pg_dump: [archiver (db)] connection to database "Segmentation Fault (core
> dumped)

This might already be fixed in CVS:

http://archives.postgresql.org/pgsql-committers/2005-07/msg00551.php
http://archives.postgresql.org/pgsql-patches/2005-07/msg00501.php

--
Michael Fuhr

---------------------------(end of broadcast)---------------------------
TIP 1: if posting/reading through Usenet, please send an appropriate
       subscribe-nomail command to [hidden email] so that your
       message can get through to the mailing list cleanly