Re: dsa_allocate() faliure

From: Jakub Glapa <jakub(dot)glapa(at)gmail(dot)com>
To: pryzby(at)telsasoft(dot)com
Cc: pgsql-performance(at)postgresql(dot)org
Subject: Re: dsa_allocate() faliure
Date: 2018-11-23 14:31:41
Message-ID: CAJk1zg3nCqG2fo_vg2RwOW6s4TjKnnnqDTrFN4FQMVAT5XEbMQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers pgsql-performance

Hi Justin, I've upgrade to 10.6 but the error still shows up:

psql db(at)host as user => select version();
version

─────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────
PostgreSQL 10.6 (Ubuntu 10.6-1.pgdg16.04+1) on x86_64-pc-linux-gnu,
compiled by gcc (Ubuntu 5.4.0-6ubuntu1~16.04.10) 5.4.0 20160609, 64-bit
(1 row)

Time: 110.512 ms

psql db(at)host as user => select <COLUMNS> from fa where client_id in
(<IDS>) and datetime >= '2018/01/01' and ((dims ? 'p' and dimensions ?
'mcp') or (datasource in ('FA', 'GA'))) and not datasource = 'M' GROUP BY
datasource, dims ->'ct', dimensions ->'mct', dims -> 'p', dims -> 'sp';
ERROR: XX000: dsa_allocate could not find 7 free pages
CONTEXT: parallel worker
LOCATION: dsa_allocate_extended, dsa.c:729
Time: 131400.831 ms (02:11.401)

the above is execute with max_parallel_workers=8
If I set it to max_parallel_workers=0 I also get and my connection is being
closed (but the server is alive):

psql db(at)host as user => set max_parallel_workers=0;
SET
Time: 89.542 ms
psql db(at)host as user => SELECT <QUERY>;
FATAL: XX000: dsa_allocate could not find 7 free pages
LOCATION: dsa_allocate_extended, dsa.c:729
SSL connection has been closed unexpectedly
The connection to the server was lost. Attempting reset: Succeeded.
Time: 200390.466 ms (03:20.390)

--
regards,
Jakub Glapa

On Thu, Nov 22, 2018 at 5:10 PM Justin Pryzby <pryzby(at)telsasoft(dot)com> wrote:

> On Wed, Nov 21, 2018 at 03:26:42PM +0100, Jakub Glapa wrote:
> > Looks like my email didn't match the right thread:
> >
> https://www.postgresql.org/message-id/flat/CAMAYy4%2Bw3NTBM5JLWFi8twhWK4%3Dk_5L4nV5%2BbYDSPu8r4b97Zg%40mail.gmail.com
> > Any chance to get some feedback on this?
>
> In the related thread, it looks like Thomas backpatched a fix to v10, and
> so I
> guess this should be resolved in 10.6, which was released couple weeks ago.
>
> https://www.postgresql.org/message-id/CAEepm%3D0QxoUSkFqYbvmxi2eNvvU6BkqH6fTOu4oOzc1MRAT4Dw%40mail.gmail.com
>
> Could you upgrade and check ?
>
> 38763d67784c6563d08dbea5c9f913fa174779b8 in master
>
> |commit ba20d392584cdecc2808fe936448d127f43f2c07
> |Author: Thomas Munro <tmunro(at)postgresql(dot)org>
> |Date: Thu Sep 20 15:52:39 2018 +1200
> |
> | Fix segment_bins corruption in dsa.c.
>
> Justin
>

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Petr Jelinek 2018-11-23 14:40:18 Re: row filtering for logical replication
Previous Message Arthur Zakirov 2018-11-23 14:29:00 Re: Add extension options to control TAP and isolation tests

Browse pgsql-performance by date

  From Date Subject
Next Message Justin Pryzby 2018-11-23 16:10:28 Re: dsa_allocate() faliure
Previous Message Justin Pryzby 2018-11-22 22:40:51 Re: Performance impact of updating target columns with unchanged values ON CONFLICT