Re: BUG #17842: Adding a qual to a working query gets bogus syntax error

From: "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>
To: Hans Buschmann <buschmann(at)nidsa(dot)net>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, PostgreSQL Bug List <pgsql-bugs(at)lists(dot)postgresql(dot)org>
Subject: Re: BUG #17842: Adding a qual to a working query gets bogus syntax error
Date: 2023-03-14 19:26:41
Message-ID: CAKFQuwZ=+eQtJh5d1fmqS1nYWfm9c8JrDV=OZr2ja6PgMW0AeQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Tue, Mar 14, 2023, 12:08 Hans Buschmann <buschmann(at)nidsa(dot)net> wrote:

>
> I think this qual pushdown is dangerous, because it is applied before the
> join and so includes invalid cases.
>

Well, it's better than any alternative that is more expensive even when the
data in question isn't prone to parsing problems. We optimize for the
common case of consistent normalized data. You have tools if you need to
operate with bad data.

David J.

> tom lane
>

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message hubert depesz lubaczewski 2023-03-14 19:33:10 pg_read_server_files doesn't let me use pg_ls_dir() or pg_read_file?
Previous Message Hans Buschmann 2023-03-14 19:07:59 AW: BUG #17842: Adding a qual to a working query gets bogus syntax error