Re: Is a VACUUM or ANALYZE necessary after logical replication?

Στις 16/6/24 02:13, ο/η Adrian Klaver έγραψε: On 6/15/24 15:55, Koen De Groote wrote: I've gone over all of https://www.postgresql.org/docs/current/logical-replication.html and the only mentions of the word "index" I could find

Re: DROP COLLATION vs pg_collation question

On Fri, 2024-06-14 at 22:08 +0200, Karsten Hilbert wrote: > Are collations per-database or per-cluster objects ? Each database has its own "pg_collation" catalog table. So they are local to the database, but the collations themselves are defined by an external library, so the implementation is sh

Re: Is a VACUUM or ANALYZE necessary after logical replication?

On 6/15/24 15:55, Koen De Groote wrote: I've gone over all of https://www.postgresql.org/docs/current/logical-replication.html and the only mentions of the word "index" I could find was in relation to replica identity and examp

Is a VACUUM or ANALYZE necessary after logical replication?

I've gone over all of https://www.postgresql.org/docs/current/logical-replication.html and the only mentions of the word "index" I could find was in relation to replica identity and examples of table definitions showing primary key indexes. Nothing is said about indexes. Maybe for good reason, may

Re: Design for dashboard query

> > > On Sat, 15 Jun 2024 at 6:54 PM, sud wrote: > >> Hello All, >> >> Its postgres version 15.4. We are having a requirement in which >> aggregated information for all the users has to be displayed on the UI >> screen. It should show that information on the screen. So basically, it >> would be sc

Re: pgstattuple - can it/does it provide stats by partition?

On Sat, Jun 15, 2024 at 9:47 AM Dragam wrote: > Hi all, > > As the title says - does (and/or can) pgstattuple provide a breakdown by > partition? > > Partitions are tables, created via CREATE TABLE. I know from experience that it works on inheritance tables; what happens wh

Re: Design for dashboard query

Have you tried creating an index on the user ID column? Scanning the entire table to apply granular filters on a few attributes seems unnecessary. Materialised views make sense if you want to aggregate some columns and query a subset of the data but would recommend trying indexes first. Finally,

pgstattuple - can it/does it provide stats by partition?

Hi all, As the title says - does (and/or can) pgstattuple provide a breakdown by partition? Any further info needed, please let me know. TIA and rgs, Dragam Envoyé avec la messagerie sécurisée [Proton Mail.](https://proton.me/)

Design for dashboard query

Hello All, Its postgres version 15.4. We are having a requirement in which aggregated information for all the users has to be displayed on the UI screen. It should show that information on the screen. So basically, it would be scanning the full table data which is billions of rows across many mont