On Thu, 26 Sept 2024 at 13:21, Yugo Nagata wrote:
> By the way, this is not mentioned in CREATE MATERIALIZED VIEW
> documentation, although
> we can find in REFRESH MATERIALIZED VIEW doc. So, I sent the doc patch in
> [1],
> and create a commitfest entry [2].
>
Thanks.
I suggest adding CREATE I
On Thu, 26 Sept 2024 at 12:22, Tom Dunstan wrote:
> I presume that this is related to the work in 17 around using restricted
> search paths in more places, but it's just a guess. CREATE INDEX isn't
> mentioned in the release notes.
>
Reading a bit closer yields:
> Fun
Hi all
While testing out 17 RC1 I found that a construct that previously worked
has now stopped working:
CREATE OR REPLACE FUNCTION index_truncate(src TEXT) RETURNS TEXT AS $$
SELECT LOWER(LEFT(src, 100));
$$ LANGUAGE SQL;
CREATE OR REPLACE FUNCTION join_for_index(TEXT [])
RETURNS TEXT LANGU
On Wed, 14 Jun 2023 at 19:14, Tomas Vondra
wrote:
> > ...So we'd want the same index usage as
> > =ANY(array) but would like faster row checking than we get with an array
> > when other indexes are used.
>
> We kinda already do this since PG14 (commit 50e17ad281), actually. If
> the list is long
On Mon, 12 Jun 2023 at 22:37, Tomas Vondra
wrote:
> Perhaps. So you're proposing to have this as a regular built-in type?
> It's hard for me to judge how popular this feature would be, but I guess
> people often use arrays while they actually want set semantics ...
>
Perspective from a potential
(Resent with subscribed email address, thanks gmail)
Hi Andres, thanks for the extremely fast review!
On 27 April 2018 at 11:46, Andres Freund wrote:
>
> > I don't see any tests for auto_explain so haven't added any test cases.
>
>> > Happy to do so if that's deemed necessary.
>
>>
> I'd be in
Hi all
This patch allows a user to configure auto_explain to log to NOTICE instead
of the server log. This allows automated testing of application-generated
queries to ensure correct plans etc from code that can inspect returned
notices but not the server log.
I don't see any tests for auto_expla
