| From: | Thomas Munro <thomas(dot)munro(at)enterprisedb(dot)com> |
|---|---|
| To: | Bartosz Polnik <bartoszpolnik(at)gmail(dot)com> |
| Cc: | David Rowley <david(dot)rowley(at)2ndquadrant(dot)com>, PostgreSQL mailing lists <pgsql-bugs(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: BUG #15577: Query returns different results when executed multiple times |
| Date: | 2019-01-07 12:19:32 |
| Message-ID: | CAEepm=0yv2qNDM_JfiakqQO3EqYNhQZjNCAX=fK8Cuhz6_RO4Q@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On Mon, Jan 7, 2019 at 10:29 PM Bartosz Polnik <bartoszpolnik(at)gmail(dot)com> wrote:
>
> > Can you confirm if there are concurrent changes being made to table_b
> > perhaps while the query is running?
>
> I confirm. There are no concurrent changes being made and I'm the only client connecting to that db.
>
> > Do you still get the variation with an otherwise idle database with no
> > open transactions that's just received a complete VACUUM?
>
> I executed VACUUM (FULL, ANALYZE) on all tables from the query, but I'm still getting different results.
>
> With your script, I'm always getting the same output, so it must be something else.
What do you get if you run it with SET force_parallel_mode = on?
--
Thomas Munro
http://www.enterprisedb.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bartosz Polnik | 2019-01-07 12:56:09 | Re: BUG #15577: Query returns different results when executed multiple times |
| Previous Message | PG Bug reporting form | 2019-01-07 12:14:17 | BUG #15579: Adding a column with default from configuration parameter fails on 11.1 |