Hi,
I also tested the patch on Linux mint 22.1 with the btrfs and ext4
partitions. I generated some data and the outcome looks good:
postgres=# \db+
List of tablespaces
Name | Owner | Location | Access
privile
That is expected because AccessExclusiveLock is acquired on the existing
matview. This is also the case for CREATE OR REPLACE VIEW.
Right, had this case many times.
My initial idea, while writing the patch, was that one could replace the
matview without populating it and then run the conc
Hi,
+1 for this feature.
Replacing Matviews
--
With patch 0001, a matview can be replaced without having to drop it and
its dependent objects. In our use case it is no longer necessary to
define the actual query in a separate view. Replacing a matview works
analogous to CREA
Hi,
I just built postgresql on macos sonoma (v14) and I had to install the
following packages:
* * icu - https://ports.macports.org/port/icu/
* * pkg - https://ports.macports.org/port/pkgconfig/
I don't see anything related to this on
https://www.postgresql.org/docs/devel/installation-pla
Hi,
However, as you said, for most use cases, pg_stat_statements and
log_statement may be sufficient.
I would like to withdraw this proposal.
Well, they either require extensions or parameters to be set properly.
One advantage I see to store those kind of information is that it can be
queri