This is a discussion on BUG #1848: Segfault with pg_dump when database name omitted within the pgsql Bugs forums, part of the PostgreSQL category; --> The following bug has been logged online: Bug reference: 1848 Logged by: Eric Boutin Email address: boutiner@gmail.com PostgreSQL version: ...
| |||||||
| Register | FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
| ||||
| The following bug has been logged online: Bug reference: 1848 Logged by: Eric Boutin Email address: boutiner@gmail.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@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 |
| ||||
| 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...7/msg00551.php http://archives.postgresql.org/pgsql...7/msg00501.php -- Michael Fuhr ---------------------------(end of broadcast)--------------------------- TIP 1: if posting/reading through Usenet, please send an appropriate subscribe-nomail command to majordomo@postgresql.org so that your message can get through to the mailing list cleanly |