The problem appears to exist in 7.0.0 as well as 7.0.2.
However I have found a solution/workaround. The queries work correctly
after performing a vacuum on the database in question.
Why would vacuum make any difference in what results a query returns?
My understanding of the vacuum process is that it shouldn't have any
impact on the current data, but only cleans up and compacts the files.
thanks,
--Barry
PS I only ran 'vacuum' to fix the problem not 'vacuum analyze'I am having the exact same problem. I am quite sure this
usedto work
in 7.0.0, but it certainly seems broken under 7.0.2. Does anyone have a
solution? I am going to try to reinstall 7.0.0 to verify that it worked
in that version.
thanks,
--Barry
Zlatko Calusic wrote:
>
> Hi!
>
> Not long after I resolved my last problem with indices ('vaccum
> analyze'), I stumbled upon another.
>
> Check this:
>
> filedb=# select file from filenew where file like '/home/zcalusic/rcs%';
>
> returns
>
> file
> ----------------------------------------------
> /home/zcalusic/rcs
> /home/zcalusic/rcs/linux
> /home/zcalusic/rcs/linux/0_REPORTING-,v
> /home/zcalusic/rcs/linux/10_bug-list.t,v
> /home/zcalusic/rcs/linux/11_00-INDEX,v
> ...
>
> but if I add one '/' before wildcard '%' (as I initially would like to
> do it):
>
> filedb=# select file from filenew where file like '/home/zcalusic/rcs/%';
> file
> ------
> (0 rows)
>
> No rows???
>
> How can that be, when output above shows I DO have rows that satisfy
> this query?
> --
> Zlatko
