| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Thomas Munro <thomas(dot)munro(at)enterprisedb(dot)com> |
| Cc: | Michael Paquier <michael(dot)paquier(at)gmail(dot)com>, Alexander Voytsekhovskyy <young(dot)inbox(at)gmail(dot)com>, PostgreSQL Bugs <pgsql-bugs(at)postgresql(dot)org> |
| Subject: | Re: BUG in 10.1 - dsa_area could not attach to a segment that has been freed |
| Date: | 2017-11-29 00:33:30 |
| Message-ID: | CA+Tgmob=UfOwbJCP9QVAQVSo0LPq8t-w-BtoRKDTzDGzmVZUbA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On Tue, Nov 28, 2017 at 7:04 PM, Thomas Munro
<thomas(dot)munro(at)enterprisedb(dot)com> wrote:
> Hmm. Well, it's the same error message but I don't think it's the
> same: that other thread was about C extension code using APIs
> incorrectly. This is parallel query, which shouldn't reach that error
> unless all the backends detach before one backend tries to attach,
> which I wouldn't normally expect to happen unless something else went
> wrong first.
Why not? Can't it just be that the workers are slow getting started?
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Thomas Munro | 2017-11-29 01:17:55 | Re: BUG in 10.1 - dsa_area could not attach to a segment that has been freed |
| Previous Message | Thomas Munro | 2017-11-29 00:04:34 | Re: BUG in 10.1 - dsa_area could not attach to a segment that has been freed |