Bug #731: Same SQL produces different results before and after VACUUM FULL - Mailing list pgsql-bugs

From pgsql-bugs@postgresql.org
Subject Bug #731: Same SQL produces different results before and after VACUUM FULL
Date
Msg-id 20020807105913.82E764759FF@postgresql.org
Whole thread Raw
Responses Re: Bug #731: Same SQL produces different results before and after VACUUM FULL  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-bugs
Henry  (henry@ssc-ltd.com) reports a bug with a severity of 1
The lower the number the more severe it is.

Short Description
Same SQL produces different results before and after VACUUM FULL

Long Description
We have run the SQL statement below before and after VACUUM FULL.
Before VACUUM FULL, it returns 3615 records.
After VACUUM FULL, it return 34123 records which is the result I expect.
Before VACUUM FULL, if I change the LEFT OUTER JOIN to join the table a, it returns 34123 records.

I have a daily backup job which executes VACUUM ANALYSE daily.

I don't know what causes the problem.  Please help!!!!


Sample Code

        SELECT *
        from (SELECT pbdedup_party_1.party_id
              from pbdedup_party_1
              where pbdedup_party_1.batch_no = ?
              UNION
              SELECT pbdedup_party_2.party_id
              from pbdedup_party_2
              where pbdedup_party_2.batch_no = ?
              ) as a
           , pb_person
                left outer join pbdedup_person_parts ON pb_person.party_id = pbdedup_person_parts.party_id
        where a.party_id = pb_person.party_id



No file was uploaded with this report

pgsql-bugs by date:

Previous
From: Adam Walczykiewicz
Date:
Subject: can't create plpgsql language on SCO 5 - postgresql 7.2.1 from Skunkware
Next
From: pgsql-bugs@postgresql.org
Date:
Subject: Bug #732: LIMIT clause bugs with insert...select