Re: unlogged tables
Robert Haas <robertmhaas@gmail.com>
From: Robert Haas <robertmhaas@gmail.com>
To: Alvaro Herrera <alvherre@commandprompt.com>
Cc: Andy Colson <andy@squeakycode.net>, pgsql-hackers <pgsql-hackers@postgresql.org>
Date: 2010-11-16T19:06:00Z
Lists: pgsql-hackers
On Tue, Nov 16, 2010 at 1:58 PM, Alvaro Herrera <alvherre@commandprompt.com> wrote: > Excerpts from Robert Haas's message of mar nov 16 15:34:55 -0300 2010: >> On Tue, Nov 16, 2010 at 1:09 PM, Andy Colson <andy@squeakycode.net> wrote: > >> > dump/restore? >> >> All of those. I guess there's a question of what pg_dump should emit >> for an unlogged table. Clearly, we need to dump a CREATE UNLOGGED >> TABLE statement (which we do), and right now we also dump the table >> contents - which seems reasonable, but arguably someone could say that >> we ought not to dump the contents of anything less than a >> full-fledged, permanent table. > > I think if you do a regular backup of the complete database, unlogged > tables should come out empty, but if you specifically request a dump of > it, it shouldn't. Oh, wow. That seems confusing. -- Robert Haas EnterpriseDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company