tglbot (@regardstomlane) 's Twitter Profile
tglbot

@regardstomlane

I am a bot relaying some Postgres mailing list excerpts from Postgres veteran Tom Lane.

ID: 1539323982

linkhttps://github.com/uhoh-itsmaciek/regardstomlane calendar_today22-06-2013 19:24:51

13,13K Tweet

428 Takipçi

10 Takip Edilen

tglbot (@regardstomlane) 's Twitter Profile Photo

In v12 (and probably earlier, didn't look) Table 9.45 defines @> as "Does the left JSON value contain the right JSON path/value entries at the top level?" [1].

tglbot (@regardstomlane) 's Twitter Profile Photo

But the answer to that does not seem difficult to me: remember who issued the ALTER and see if they still have SET privilege at the time we activate a particular entry.

tglbot (@regardstomlane) 's Twitter Profile Photo

The reason this wasn't a bug before 86dc90056 is that any given plan tree could have only one target relation, so there was not anything else to suppress.

tglbot (@regardstomlane) 's Twitter Profile Photo

You could arbitrarily define months as 30 days and days as 24 hours, which is what some other interval functions do, and then the double result would be well-defined; but how useful is it really?

tglbot (@regardstomlane) 's Twitter Profile Photo

We've done something similar before, and it seems a lot safer than having basically different logic in v16 than earlier branches.

tglbot (@regardstomlane) 's Twitter Profile Photo

It's especially pointless when the main pgindent run for v16 is going to happen today (as soon as I get done clearing out my other queue items).

tglbot (@regardstomlane) 's Twitter Profile Photo

It's not entirely clear to me that the EPQ state it sets up is ever used; but if it is I think it is okay as I have it here, because it looks like those invocations always have just one result relation in the plan, so there aren't any "extra" result rels that need to be blocked.

tglbot (@regardstomlane) 's Twitter Profile Photo

I chose to replace the tuple_table field, because it was in a convenient spot and it seemed like the field least likely to have any outside code referencing it.