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

Re: pg_dump pretty_print

From: Peter Eisentraut <peter_e(at)gmx(dot)net>
To: pgsql-patches(at)postgresql(dot)org
Cc: "Greg Sabino Mullane" <greg(at)turnstep(dot)com>
Subject: Re: pg_dump pretty_print
Date: 2007-01-23 09:13:44
Message-ID: 200701231013.45125.peter_e@gmx.net (view raw or flat)
Thread:
Lists: pgsql-hackerspgsql-patches
Am Montag, 22. Januar 2007 20:53 schrieb Greg Sabino Mullane:
> Since we already do make some concessions as far as
> making the dump file human-readable, offering this as an *optional* flag
> seems (mostly) harmless.

The harm here is that under undefined circumstances a dump file will not be a 
proper and robust representation of the original database, which would add 
significant confusion and potential for error.

-- 
Peter Eisentraut
http://developer.postgresql.org/~petere/

In response to

Responses

pgsql-hackers by date

Next:From: ITAGAKI TakahiroDate: 2007-01-23 09:28:55
Subject: Re: Free space management within heap page
Previous:From: Pavan DeolaseeDate: 2007-01-23 09:03:11
Subject: Re: Free space management within heap page

pgsql-patches by date

Next:From: Takayuki TsunakawaDate: 2007-01-23 09:50:06
Subject: Re: [HACKERS] Win32 WEXITSTATUS too
Previous:From: Achilleas MantziosDate: 2007-01-23 08:52:28
Subject: Re: server process (PID xxx) was terminated by signal 7

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