Federico Di Gregorio <[EMAIL PROTECTED]> writes:
> ok. attached to this mail is a dump in tar format. this is the EXPLAIN
> ANALYZE of a query *before* the dump:
> EXPLAIN ANALYZE SELECT * FROM BOL_USC
> WHERE UPPER(RPAD("RAGIONE",80)||TO_CHAR("IDBOL_USC",'S00')) >=
> ' +000
On Thu, 2004-10-14 at 06:54 -0400, Tom Lane wrote:
> "PostgreSQL Bugs List" <[EMAIL PROTECTED]> writes:
> > After a pg_dump/pg_restore (using the tar format) queries that were using
> > the indices don't use them anymore until the indices are dropped and
> > recreated. After that the indices are
Federico Di Gregorio <[EMAIL PROTECTED]> writes:
> On Thu, 2004-10-14 at 06:54 -0400, Tom Lane wrote:
>> I do not believe that you remembered to ANALYZE after restore.
> unfortunately for your belief, i remembered. :)
> also, this problem can be replicated at will. i can send a dump that
> expose
"PostgreSQL Bugs List" <[EMAIL PROTECTED]> writes:
> After a pg_dump/pg_restore (using the tar format) queries that were using
> the indices don't use them anymore until the indices are dropped and
> recreated. After that the indices are used the correct way.
I do not believe that you remembere
The following bug has been logged online:
Bug reference: 1286
Logged by: Federico Di Gregorio
Email address: [EMAIL PROTECTED]
PostgreSQL version: 7.4.5
Operating system: Debian GNU/Linux sarge
Description:indices not used after a pg_restore
Details:
We have a
