validly - Search results in mailing lists
Mailing lists >> pgsql-performance >> Thread
2024-10-24 09:43:53 | Adding exclusion constraint in a big table (Marcelo Fernandes)
with a NOT VALID condition either. Do you folks have any recommendations for this situation?
Mailing lists >> pgsql-performance >> Thread
2024-03-05 20:13:13 | Re: Separate 100 M spatial data in 100 tables VS one big table (Tomas Vondra)
valid option - and it's much better than the view with a UNION of all the per-department
Mailing lists >> pgsql-performance >> Thread
2023-08-11 04:49:24 | Re: Partitioning update-heavy queue with hash partitions vs partial indexes (David Rowley)
valid for the given query must consider each index one at a time and validate
Mailing lists >> pgsql-performance >> Thread
2023-03-14 17:54:35 | Re: multicolumn partitioning help (Justin Pryzby)
valid values of the corresponding partition key columns for this partition, whereas those in the TO list
Mailing lists >> pgsql-performance >> Thread
2023-02-08 19:47:07 | Re: Domain check taking place unnecessarily? (Laurenz Albe)
VALID and later run ALTER TABLE ... VALIDATE CONSTRAINT ..., which takes a while too, but does
Mailing lists >> pgsql-performance >> Thread >> Search in thread (2)
2022-12-19 09:47:34 | Re: Fwd: temp_file_limit? (Frits Jalvingh)
valid bug" is concerned: I had hoped this would be per session, as this at least
Mailing lists >> pgsql-performance >> Thread
2022-04-18 14:02:49 | How to find the final transformed query in postgresql (Goti)
valid questions. I would like to know if postgres performs any transformations when it does
Mailing lists >> pgsql-performance >> Thread
2022-03-23 14:49:39 | Re: Using system tables directly takes many hours, using temp tables with no indexes takes (Lars Aksel Opsahl)
valid for just some few seconds before having to run analyze again and that takes
Mailing lists >> pgsql-performance >> Thread
2021-10-13 19:05:35 | Re: Lock contention high (Peter Geoghegan)
valid results generally require that you use lots of warehouses to get a very large
Mailing lists >> pgsql-performance >> Thread
2021-10-10 22:09:32 | Re: Better, consistent instrumentation for postgreSQL using a similar API as Oracle (Franck Pachot)
valid OS for enterprises, when instrumentation reached the same level as we got on Unix
Mailing lists >> pgsql-performance >> Thread
2021-07-22 11:32:51 | Partitioned table statistics vs autoanalyze (Kamil Frydel)
valid in PG 13 and does it apply to declarative partitioning as well? Is running
Mailing lists >> pgsql-performance >> Thread
2021-05-24 14:11:39 | Re: Optimising outer joins in the presence of non-nullable references (Tom Lane)
valid at every instant. Maybe. Aside from semantic correctness issues, the big question would be whether
Mailing lists >> pgsql-performance >> Thread
2021-05-17 22:31:50 | Re: Index and statistics not used (David Rowley)
valid? (psql's \d table2 would show you INVALID if they're not.) does: SHOW
Mailing lists >> pgsql-performance >> Thread
2021-04-24 19:52:44 | Re: Does btrfs on Linux have a negative performance impact for PostgreSQL 13? (Tomas Vondra)
valid, but maybe btrfs improved a lot - I haven't done any testing since then
Mailing lists >> pgsql-performance >> Thread
2021-04-13 23:16:46 | Re: LWLocks by LockManager slowing large DB (Tom Lane)
valid index relation */ validIndex = toast_open_indexes(toastrel, - RowExclusiveLock, + lock, &toastidxs, &num_indexes); @@ -489,7 +490,7 @@ toastrel