Yugo NAGATA writes:
> Thank you for your reviewing and editing the patch!
> I agree with your proposal on the error message handling.
Cool, pushed v4 then.
regards, tom lane
On Mon, 30 Dec 2024 16:06:06 -0500
Tom Lane wrote:
> Yugo NAGATA writes:
> > On Wed, 20 Nov 2024 12:43:16 -0500
> > Tom Lane wrote:
> >> ... It seems to me that we should
> >> think about this, for MVs as well as those other object types,
> >> as fundamentally a dependency problem. That is, th
Yugo NAGATA writes:
> On Wed, 20 Nov 2024 12:43:16 -0500
> Tom Lane wrote:
>> ... It seems to me that we should
>> think about this, for MVs as well as those other object types,
>> as fundamentally a dependency problem. That is, the reason
>> we can't allow a reference to an ENR in a long-lived
On Wed, 20 Nov 2024 12:43:16 -0500
Tom Lane wrote:
> Yugo NAGATA writes:
> >> You could even argue that case 2 isn't good enough either,
> >> and we should be delivering a specific error message saying
> >> that an ENR can't be used in a view/matview. To do that,
> >> we'd likely need to pass d
On Fri, 15 Nov 2024 at 13:37, Yugo NAGATA wrote:
>
> On Sun, 03 Nov 2024 13:42:33 -0500
> Tom Lane wrote:
>
> > Yugo Nagata writes:
> > > While looking into the commit b4da732fd64e936970f38c792f8b32c4bdf2bcd5,
> > > I noticed that we can create a materialized view using Ephemeral Named
> > > Rel
Yugo NAGATA writes:
>> You could even argue that case 2 isn't good enough either,
>> and we should be delivering a specific error message saying
>> that an ENR can't be used in a view/matview. To do that,
>> we'd likely need to pass down the QueryEnvironment in more
>> places not fewer.
> We can
On Fri, Nov 15, 2024 at 05:36:47PM +0900, Yugo NAGATA wrote:
> I agree that raising an internal error is not enough. I attached a updated
> patch that outputs a message saying that an ENR can't be used in a matview.
Hmm.. To get a better idea of the scope you are foreseeing here,
should this incl
On Sun, 03 Nov 2024 13:42:33 -0500
Tom Lane wrote:
> Yugo Nagata writes:
> > While looking into the commit b4da732fd64e936970f38c792f8b32c4bdf2bcd5,
> > I noticed that we can create a materialized view using Ephemeral Named
> > Relation in PostgreSQL 16 or earler.
>
> Yeah, we should reject th
Yugo Nagata writes:
> While looking into the commit b4da732fd64e936970f38c792f8b32c4bdf2bcd5,
> I noticed that we can create a materialized view using Ephemeral Named
> Relation in PostgreSQL 16 or earler.
Yeah, we should reject that, but I feel like this patch is not
ambitious enough, because t
On Fri, 26 Jul 2024 at 12:07, Yugo Nagata wrote:
>
> Hi,
>
> While looking into the commit b4da732fd64e936970f38c792f8b32c4bdf2bcd5,
> I noticed that we can create a materialized view using Ephemeral Named
> Relation in PostgreSQL 16 or earler.
>
>
> postgres=# create table tbl (i int);
> CREATE T
Hi,
While looking into the commit b4da732fd64e936970f38c792f8b32c4bdf2bcd5,
I noticed that we can create a materialized view using Ephemeral Named
Relation in PostgreSQL 16 or earler.
postgres=# create table tbl (i int);
CREATE TABLE
^
postgr
11 matches
Mail list logo
