Re: Syntax for partitioning
От | Marko Tiikkaja |
---|---|
Тема | Re: Syntax for partitioning |
Дата | |
Msg-id | 4B0302F6.9020808@cs.helsinki.fi обсуждение исходный текст |
Ответ на | Re: Syntax for partitioning (Jaime Casanova <jcasanov@systemguards.com.ec>) |
Ответы |
Re: Syntax for partitioning
|
Список | pgsql-hackers |
Jaime Casanova wrote: >> * If a table with the same name already exists when a partition >> is created, the table is re-used as partition. This behavior >> is required for pg_dump to be simple. >> > > i guess the table must be empty, if not we should be throw an error... > and i actually prefer some more explicit syntax for this not just > reusing a table I'd be OK with only a notification - even if the table wasn't empty -, similar to how inheritance combines rows currently. The patch currently silently reuses the table unless it has rows which don't satisfy the CHECK constraint, in which case it gives you the default CHECK constraint error. >> PARTITION name VALUES LESS THAN { range_upper | MAXVALUE } >> | PARTITION name VALUES IN ( list_value [,...] | DEFAULT ) >> > > i remember someone making a comment about actually using operators > instead of LESS THEN and family That doesn't sound like a bad idea.. Regards, Marko Tiikkaja
В списке pgsql-hackers по дате отправления: