From: | Carlos Henrique Reimer <carlos(dot)reimer(at)opendb(dot)com(dot)br> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: User function canceling VACUUMDB utility |
Date: | 2010-09-13 10:16:34 |
Message-ID: | AANLkTi=4fRsph+7Lbxgv5+ZazDmdOcEh5JabnoRofExD@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Hi,
Yes, once correct schema was included in the search_path, VACUUM and ANALYZE
run fine again.
Thank you!
On Fri, Sep 10, 2010 at 11:38 AM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Carlos Henrique Reimer <carlos(dot)reimer(at)opendb(dot)com(dot)br> writes:
> > Yes, you're right! I found out a functional index using this function and
> > ANALYZE also cancels.
>
> > Is there a way to code this function in a way VACUUM/ANALYZE does not
> > cancel?
>
> I think your problem is probably a search_path issue, ie vacuumdb is not
> running with the "BRASIL" schema in its path so the column reference
> fails to resolve. You should be able to add the schema name to the
> %TYPE reference. Or, if you can't make that work, just don't use
> %TYPE...
>
> regards, tom lane
>
--
Reimer
47-3347-1724 47-9183-0547 msn: carlos(dot)reimer(at)opendb(dot)com(dot)br
From | Date | Subject | |
---|---|---|---|
Next Message | Sam Mason | 2010-09-13 10:33:55 | Re: Post Install / Secure PostgreSQL |
Previous Message | Craig Ringer | 2010-09-13 10:16:21 | Re: new encoding (UTF8) is incompatible with the encoding of the template database (SQL_ASCII) |