Re: Prevent COPY FREEZE on Foreign tables
| От | Zhang Mingli |
|---|---|
| Тема | Re: Prevent COPY FREEZE on Foreign tables |
| Дата | |
| Msg-id | 4b138a75-0295-4534-af66-b61d256f24fb@Spark обсуждение исходный текст |
| Ответ на | Re: Prevent COPY FREEZE on Foreign tables (Sami Imseih <samimseih@gmail.com>) |
| Список | pgsql-hackers |
On Feb 6, 2025 at 03:27 +0800, Sami Imseih <samimseih@gmail.com>, wrote:
Yeah, I'd rather error out than expect users to respond to warnings to the
effect of "hey, you told us to do something, but we did something else that
isn't what you asked us to do." That both retains the broken feature and
adds more noise, neither of which seems desirable.
I agree.
Sami
Hi,
I understand your perspective, and I'm okay with it.
Since partitioning is currently unsupported in PostgreSQL, returning an error makes sense.
My reason for the warning on foreign tables is: that mainly to inform users that the behavior is unchanged (data copied), they just need to correct their commands.
When COPY FREEZE for partitioned tables becomes supported, we’ll need to ensure that none of the partitions are foreign tables.
If we find any, the FREEZE operation won’t be applicable. However, that's a consideration for the future.
LGTM.
--
Zhang Mingli
HashData
I understand your perspective, and I'm okay with it.
Since partitioning is currently unsupported in PostgreSQL, returning an error makes sense.
My reason for the warning on foreign tables is: that mainly to inform users that the behavior is unchanged (data copied), they just need to correct their commands.
When COPY FREEZE for partitioned tables becomes supported, we’ll need to ensure that none of the partitions are foreign tables.
If we find any, the FREEZE operation won’t be applicable. However, that's a consideration for the future.
LGTM.
--
Zhang Mingli
HashData
В списке pgsql-hackers по дате отправления: