| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Joe Conway <mail(at)joeconway(dot)com> |
| Cc: | Jeff Davis <pgsql(at)j-davis(dot)com>, Andres Freund <andres(at)anarazel(dot)de>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>, Yugo Nagata <nagata(at)sraoss(dot)co(dot)jp>, amul sul <sulamul(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Subject: | Re: Hash Functions |
| Date: | 2017-06-02 16:32:53 |
| Message-ID: | CA+TgmoY1cDOZGOW_4-P_+opzm0CK32V89x+b+7bCpD2LDxBhpg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Fri, Jun 2, 2017 at 10:19 AM, Joe Conway <mail(at)joeconway(dot)com> wrote:
>> Yeah, that's not crazy. I find it a bit surprising in terms of the
>> semantics, though. SET
>> when_i_try_to_insert_into_a_specific_partition_i_dont_really_mean_it =
>> true?
>
> Maybe
> SET partition_tuple_retry = true;
> -or-
> SET partition_tuple_reroute = true;
> ?
>
> I like the idea of only rerouting when failing constraints although I
> can envision where there might be use cases where you essentially want
> to re-partition and therefore reroute everything, leading to:
>
> SET partition_tuple_reroute = (none | error | all);
Personally, I think it's more elegant to make this a pg_dump option
than to make it a server GUC, but I'm not going to spend time fighting
the server GUC idea if other people like it.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Sergey Burladyan | 2017-06-02 16:42:18 | Questions about upgrade standby with rsync |
| Previous Message | Robert Haas | 2017-06-02 16:31:30 | sketchy partcollation handling |