From: | Jeff Janes <jeff(dot)janes(at)gmail(dot)com> |
---|---|
To: | Postgres General <pgsql-general(at)postgresql(dot)org> |
Subject: | unanalyze a foreign table |
Date: | 2019-12-22 19:21:32 |
Message-ID: | CAMkU=1x0C6H-yUPimAb-kzO1FqNeHW06gNT7Dny2SY3Ua23j4Q@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
I did a manual ANALYZE of a foreign table, to see if it would make a
troublesome query better. It did, but it also made some other queries that
were previously fine to become far worse. Is there a way to undo the
analyze? I can muck around in the catalogs like below, but seems really
grotty.
delete from pg_statistic where starelid=418911;
The other option seems to be doing a `drop foreign table ... cascade`, but
then recreating all the cascaded drops is quite annoying and error prone.
I currently solved it by re-cloning my performance testing server from
upstream, but that also is not very convenient. Is directly manipulating
the catalogs really the best way?
Cheers,
Jeff
From | Date | Subject | |
---|---|---|---|
Next Message | Boylan, Ross | 2019-12-22 19:59:07 | Re: Semi-unable to add new records to table--primary key needed? |
Previous Message | Adrian Klaver | 2019-12-22 18:35:53 | Re: Semi-unable to add new records to table--primary key needed? |