| From: | Mohamed Wael Khobalatte <mkhobalatte(at)grubhub(dot)com> |
|---|---|
| To: | Michael Lewis <mlewis(at)entrata(dot)com> |
| Cc: | Daniel Verite <daniel(at)manitou-mail(dot)org>, pgsql-general <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Switching Primary Keys to BigInt |
| Date: | 2020-07-22 20:11:32 |
| Message-ID: | CABZeWdxREF+D=bZQ08SZg+AB5eU_CY4HKphPR43tC7sY_-BZvg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
>
> One presumes you may be planning to use pglogical or another similar
> solution to upgrade to a new Postgres version soon, and would have a
> convenient time then to change schema. I am curious, why not just stick
> with the single column unique index and forgo for the primary key
> constraint for now? If you are concerned about the possibility of a single
> null value being inserted, then you could add a not valid check constraint
> to enforce that for future rows.
>
Believe it or not I pitched a similar idea internally. I'll explore it in a
test run.
> Given your email domain, I can guess why you would need to absolutely
> minimize downtime.
>
Right. ;)
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Mohamed Wael Khobalatte | 2020-07-22 20:12:18 | Re: Switching Primary Keys to BigInt |
| Previous Message | Michael Lewis | 2020-07-22 19:14:47 | Re: Switching Primary Keys to BigInt |