How big is ix_tabledata_intid_timestampdate_intotherid3_intotherid2 on
disk? If you create another index with same fields, how much space does it
take? Real question- are you vacuuming aggressively enough for your
workload? Your index name seems to indicate that intotherid3 would be the
third key,
Running into a strange issue that just popped up on a few servers in my
environment and was wondering if the community had any insight into as to
what could be causing the issue.
First, a bit of background. I am running Postgres 10.11 on Windows (but
have seen similar issue on a server running 11.
Jeff Janes writes:
> On Wed, Feb 26, 2020 at 1:02 PM Guillaume Cottenceau wrote:
>
> It is actually consistent with using a restored backup on the dev
> computer, as my understanding is this comes out without any
> garbage and like a perfectly vacuumed database.
>
> I think I got that backwar
