| From: | Noah Misch <noah(at)leadboat(dot)com> |
|---|---|
| To: | Jeff Davis <pgsql(at)j-davis(dot)com> |
| Cc: | Peter Eisentraut <peter(at)eisentraut(dot)org>, Daniel Verite <daniel(at)manitou-mail(dot)org>, Robert Haas <robertmhaas(at)gmail(dot)com>, Jeremy Schneider <schneider(at)ardentperf(dot)com>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Built-in CTYPE provider |
| Date: | 2024-07-02 16:51:45 |
| Message-ID: | 20240702165145.af.nmisch@google.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Mon, Jul 01, 2024 at 06:19:08PM -0700, Jeff Davis wrote:
> On Mon, 2024-07-01 at 16:03 -0700, Noah Misch wrote:
> > An alternative would be to make pg_upgrade reject
> > operating on a cluster that contains use of $SUBJECT.
>
> That wouldn't help anyone.
Can you say more about that? For the last decade at least, I think our
standard for new features has been to error rather than allow an operation
that creates a known path to wrong query results. I think that's a helpful
standard that we should continue to follow.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2024-07-02 16:55:53 | Re: What is a typical precision of gettimeofday()? |
| Previous Message | David E. Wheeler | 2024-07-02 16:51:19 | Document DateStyle effect on jsonpath string() |