Re: Using ALTER TABLESPACE in pg_dump

From: Fabien COELHO <coelho(at)cri(dot)ensmp(dot)fr>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>, Philip Warner <pjw(at)rhyme(dot)com(dot)au>, Robert Treat <xzilla(at)users(dot)sourceforge(dot)net>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Using ALTER TABLESPACE in pg_dump
Date: 2004-10-26 06:24:04
Message-ID: Pine.LNX.4.61.0410260817240.26921@sablons.cri.ensmp.fr
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers


Dear Tom,

>> ISTM that the core business of a database is to help organize and protect
>> data, and it is plainly that. You just wish you won't need it, so it is
>> somehow "abstract", but when and if you need it, it is not "second-order"
>> at all;-) and it is much too late to redo the dump.
>
> So you create some tablespaces by hand. Big deal.

I agree that is is doable this way, although not really nice.

> This objection is not strong enough to justify an ugly, klugy definition
> for where tables get created.

I do also agree about this.

My real point is that while reading the thread quickly, I was afraid the
problem would not be better addressed at all in the coming release.

It seems that I was wrong as it does not look to be the case.
Any fix instead of nothing is fair enough for me.

Thanks for your answer, have a nice day,

--
Fabien Coelho - coelho(at)cri(dot)ensmp(dot)fr

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Simon Riggs 2004-10-26 08:49:15 Re: [PATCHES] ARC Memory Usage analysis
Previous Message Adrian Maier 2004-10-26 06:13:54 Re: [HACKERS] Question on the 8.0Beta Version