Otherwise, we need to extend the ADD CONSTRAINT syntax.
Yeah, I was wondering if there was some minimal-impact way to do that.
Shall I hold off on doing any pg_dump changes then?
Chris
---(end of broadcast)---
TIP 1: subscribe and unsubscribe commands
Otherwise, we need to extend the ADD CONSTRAINT syntax.
Yeah, I was wondering if there was some minimal-impact way to do that.
Oh, or we create ALTER CONSTRAINT :)
Chris
---(end of broadcast)---
TIP 7: don't forget to increase your free space map set
In fact, now that I think of it, the patch-as-committed already
introduces some serious headaches for pg_dump: it can't know for sure
what name will be assigned to constraint indexes (pkey and unique
indexes) so it has no good way to emit ALTER TABLE SET TABLESPACE
commands for those indexes.
I gue
Christopher Kings-Lynne <[EMAIL PROTECTED]> writes:
> Otherwise, we need to extend the ADD CONSTRAINT syntax.
Yeah, I was wondering if there was some minimal-impact way to do that.
regards, tom lane
---(end of broadcast)---
Gavin Sherry <[EMAIL PROTECTED]> writes:
> On Mon, 12 Jul 2004, Christopher Kings-Lynne wrote:
>> I vote for taking it out.
> Pull it. I added it intentionally but now I'm questioning my reasoning
> (which was, sequences might be accessed lots, people might want to put
> them somewhere intentiona
Bruce Momjian <[EMAIL PROTECTED]> writes:
> Will toast go in the same tablespace as the base table?
That is the current design, and I'd prefer to keep it that way because
anything else adds great complexity for unclear gain.
Two examples of pain points:
1. That pending patch to report a table's
On Mon, 12 Jul 2004, Christopher Kings-Lynne wrote:
> > I had forgotten that the original patch allowed that. Personally I'd
> > vote for taking it out, for the above-stated reasons --- any objections?
>
> I vote for taking it out.
Pull it. I added it intentionally but now I'm questioning my re
I had forgotten that the original patch allowed that. Personally I'd
vote for taking it out, for the above-stated reasons --- any objections?
I vote for taking it out.
Chris
---(end of broadcast)---
TIP 7: don't forget to increase your free space map
Christopher Kings-Lynne <[EMAIL PROTECTED]> writes:
>> Sequences are too small to be worth moving around, and may someday be
>> reimplemented in a fashion that doesn't use up a separate disk file for
>> each one. If we allow SET TABLESPACE on them we will be limiting our
>> future flexibility for
However, based on our feature freeze, maybe what we have now is fine and
I can just add the TODO item again.
---
Tom Lane wrote:
> Christopher Kings-Lynne <[EMAIL PROTECTED]> writes:
> >> Sequences are too small to be worth
Will toast go in the same tablespace as the base table? I can see some
advantages to splitting that to another drive for extreme cases (think
heap/toast lookups over and over again).
---
Tom Lane wrote:
> Christopher Kings-
Christopher Kings-Lynne wrote:
> > Please remove that; if I thought either one was a good idea, I would
> > have allowed it in the committed patch.
> >
> > Sequences are too small to be worth moving around, and may someday be
> > reimplemented in a fashion that doesn't use up a separate disk file
Does this patch allow setting the tablespace of sequences as well? If
so, then you will need to modify pg_dump of SERIAL sequences. Perhaps
output a ALTER TABLE/SET TABLESPACE command after the CREATE TABLE
definition to move the SERIAL sequence.
The same argument applies if it allows moving i
Please remove that; if I thought either one was a good idea, I would
have allowed it in the committed patch.
Sequences are too small to be worth moving around, and may someday be
reimplemented in a fashion that doesn't use up a separate disk file for
each one. If we allow SET TABLESPACE on them we
OK, removed.
---
Tom Lane wrote:
> Bruce Momjian <[EMAIL PROTECTED]> writes:
> > Added to TODO;
> > * Allow moving sequences and toast tables to other tablespaces
> > in case no one does it.
>
> Please remove that; if I
Tom Lane wrote:
> Christopher Kings-Lynne <[EMAIL PROTECTED]> writes:
> >> Attached is an updated ALTER TABLE ... SET TABLESPACE patch.
>
> > Does this patch allow setting the tablespace of sequences as well? If
> > so, then you will need to modify pg_dump of SERIAL sequences. Perhaps
> > outp
Bruce Momjian <[EMAIL PROTECTED]> writes:
> Added to TODO;
> * Allow moving sequences and toast tables to other tablespaces
> in case no one does it.
Please remove that; if I thought either one was a good idea, I would
have allowed it in the committed patch.
Sequences are too small to be wo
Applied by Tom.
---
Gavin Sherry wrote:
> Hi all,
>
> Attached is an updated ALTER TABLE ... SET TABLESPACE patch.
>
> It uses the block by block copy mechanism proposed by Tom and handles i)
> ALTER TABLE and ii) Co
Christopher Kings-Lynne <[EMAIL PROTECTED]> writes:
>> Attached is an updated ALTER TABLE ... SET TABLESPACE patch.
> Does this patch allow setting the tablespace of sequences as well? If
> so, then you will need to modify pg_dump of SERIAL sequences. Perhaps
> output a ALTER TABLE/SET TABLESP
I realize this still need WAL work, but we should get this in.
Your patch has been added to the PostgreSQL unapplied patches list at:
http://momjian.postgresql.org/cgi-bin/pgpatches
I will try to apply it within the next 48 hours.
---
Attached is an updated ALTER TABLE ... SET TABLESPACE patch.
It uses the block by block copy mechanism proposed by Tom and handles i)
ALTER TABLE and ii) Copying of TOAST tables and the TOAST
table's index.
It doesn't handle copying of system tables (pg_largeobject) and, in the
interests of c
On Wed, 2004-06-30 at 22:29, Gavin Sherry wrote:
> On Thu, 1 Jul 2004, Gavin Sherry wrote:
> Oh, and it doesn't handle WAL. Tom mentioned/agreed that btree's method of
> dumping whole pages into WAL would be the best/most efficient way to
> journaling this and that the btree code should be general
On Thu, 1 Jul 2004, Gavin Sherry wrote:
> Hi all,
>
> Attached is an updated ALTER TABLE ... SET TABLESPACE patch.
>
> It uses the block by block copy mechanism proposed by Tom and handles i)
> ALTER TABLE and ii) Copying of TOAST tables and the TOAST
> table's index.
>
> It doesn't handle c
Hi all,
Attached is an updated ALTER TABLE ... SET TABLESPACE patch.
It uses the block by block copy mechanism proposed by Tom and handles i)
ALTER TABLE and ii) Copying of TOAST tables and the TOAST
table's index.
It doesn't handle copying of system tables (pg_largeobject) and, in the
int
24 matches
Mail list logo
