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

BUG #1848: Segfault with pg_dump when database name omitted

From: "Eric Boutin" <boutiner(at)gmail(dot)com>
To: pgsql-bugs(at)postgresql(dot)org
Subject: BUG #1848: Segfault with pg_dump when database name omitted
Date: 2005-08-25 18:41:59
Message-ID: 20050825184159.70707F0D88@svr2.postgresql.org (view raw or flat)
Thread:
Lists: pgsql-bugs
The following bug has been logged online:

Bug reference:      1848
Logged by:          Eric Boutin
Email address:      boutiner(at)gmail(dot)com
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(at)imelda ~]$ pg_dump -U appserv -t tbl_dossiers -s
pg_dump: [archiver (db)] connection to database "Segmentation Fault (core
dumped)
[eric(at)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

Responses

pgsql-bugs by date

Next:From: Matthew ManuelDate: 2005-08-25 20:05:11
Subject: auto type casting bug
Previous:From: vishal saberwalDate: 2005-08-25 18:25:06
Subject: Re: Ref: BUG#1321: SSL error: sslv3 alert handshake failure

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