| From: | Noah Misch <noah(at)leadboat(dot)com> |
|---|---|
| To: | Simon Riggs <simon(at)2ndquadrant(dot)com> |
| Cc: | Josh Berkus <josh(at)agliodbs(dot)com>, Andres Freund <andres(at)2ndquadrant(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: No-rewrite timestamp<->timestamptz conversions |
| Date: | 2019-02-26 20:12:35 |
| Message-ID: | 20190226201235.GB1655734@rfd.leadboat.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, Feb 26, 2019 at 02:29:01PM +0000, Simon Riggs wrote:
> Looks good, would need docs.
The ALTER TABLE page just says "old type is either binary coercible to the new
type or an unconstrained domain over the new type." Avoiding rewrites by way
of a prosupport function or the at-timestamp-v2.patch approach is essentially
another way to achieve binary coercion. So far, we haven't documented the
individual data types affected. Since we don't mention e.g. varchar(x) ->
varchar(x+k) explicitly, I plan not to mention timestamp explicitly.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Geoghegan | 2019-02-26 20:14:11 | Re: Remove Deprecated Exclusive Backup Mode |
| Previous Message | Markus Winand | 2019-02-26 20:07:01 | Index INCLUDE vs. Bitmap Index Scan |