From: | Morris de Oryx <morrisdeoryx(at)gmail(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | pgsql-general <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: ERROR: could not find tuple for statistics object - is there a way to clean this up? |
Date: | 2020-11-15 21:57:28 |
Message-ID: | CAKqnccgVfym7C7biDsNy_f13ijL=13-nxa3SHVSW7xiQAjA0jg@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Thanks, it's my local copy, which I drop and rebuild constantly as part of
my testing cycle. On our deployed servers, my patch and test procedures are
very strict. Locally, I like to experiment and blow things up. Well,
mission accomplished there ;-)
Thanks for taking the time to answer.
On Mon, Nov 16, 2020 at 3:34 AM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Morris de Oryx <morrisdeoryx(at)gmail(dot)com> writes:
> > After posting, I realized that this is likely a Stupid User Error. I was
> > mucking around, and did something along the lines of
> > delete from pg_statistic_ext;
> > or
> > delete from pg_stats_ext;
>
> > ...instead of DROP STATISTICS calls. Would this likely explain what I'm
> > seeing?
>
> Ah, yeah, it likely would.
>
> If this isn't a throwaway database, what you'd have to do to clear the
> errors is to find and remove the now-dangling links to the deleted objects
> in pg_depend.
>
> regards, tom lane
>
From | Date | Subject | |
---|---|---|---|
Next Message | Condor | 2020-11-16 07:15:47 | Unable to compile postgres 13.1 on Slackware current x64 |
Previous Message | Maksim Fomin | 2020-11-15 20:47:54 | Restoring database from false update |