Hi Team,
i have a table of size 2.6TB which is very prone to updates and inserts so
we have tuned autovacuum to run on it very aggressively , so the table
level bloat is fine .
Now we are facing issue with indexes on this table. the total size of all
indexes on this table is around 2.4TB.
There
Hi Teaam,
Doubt regarding the backrest restore options,
is there any way to ensure the backups are good as expected, instead of
restoring the whole cluster or database is there any other possibility to
ensure it by restoring a single file? or any other such mechanism
Thanks,
Raj
Thanks Michael.
On Mon, 6 Apr, 2020, 9:49 PM Michael Lewis, wrote:
> There is nothing native to compute this. This was asked a month or so ago.
> The best the poster came up with was a regular query on master DB which
> updates a timestamptz field. Assuming master and slave have clocks in sync,
Hi Team,
Is there a way or query to measure replication lag on logical replication
setup in terms of time ?
Thanks
Raj
@Alvaro Herrera, Can i alter the datatype of relid to oid and try ?
On Thu, Jan 16, 2020 at 12:41 AM Alvaro Herrera
wrote:
> On 2020-Jan-15, Konireddy Rajashekar wrote:
>
> > rangetest-# \d user_tables_sizes
> > Table "user_tables_sizes"
> &
tried casting to text,varchar but no luck
select u.relid,c.relnamespace::regnamespace::text,c.relname,now() as
current_time,pg_size_pretty(pg_relation_size(c.oid)) as
current_size,pg_size_pretty(u.table_size) as
previous_size,pg_size_pretty(pg_relation_size(c.oid) -
pg_relation_size(u.table_size))
I am getting ERROR: OID out of range while firing below SQL , what could be
the reason? I am joining pg_class and one user_created table to compare
tables size.
select u.relid,c.relnamespace::regnamespace::text,c.relname,now() as
current_time,pg_size_pretty(pg_relation_size(c.oid)) as
current_siz