Re:Re: ERROR: XX000: cannot update SecondarySnapshot during a parallel operation

From: fuzk <fuzk80_76(at)163(dot)com>
To: "Adrian Klaver" <adrian(dot)klaver(at)aklaver(dot)com>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re:Re: ERROR: XX000: cannot update SecondarySnapshot during a parallel operation
Date: 2019-03-14 05:54:30
Message-ID: 2fb2c6ad.74b1.1697ac42b3f.Coremail.fuzk80_76@163.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Dear Adrian,

My setting is as following.

max_parallel_workers_per_gather=32

I am looking forward to hearing from you.

Many thanks
Alan.

At 2019-03-13 22:31:11, "Adrian Klaver" <adrian(dot)klaver(at)aklaver(dot)com> wrote:
>On 3/12/19 7:54 PM, fuzk wrote:
>> Dear Sir/Madam
>>
>> I got an error when I execute the following select sentence.
>> Would you please solve the problem for me?
>
>What version of Postgres?
>
>> Thank you .
>>
>> Alan Fu.
>>
>> postgres=# \set VERBOSITY verbose
>> postgres=# SELECT
>> round(cast(coalesce(sum(ST_length(geography(geometry)))/1000,0) as
>> NUMERIC),4)||'KM' field_value from had_link;
>>
>> ERROR: XX000: cannot update SecondarySnapshot during a parallel operation
>> CONTEXT: SQL statement "SELECT proj4text FROM public.spatial_ref_sys
>> WHERE srid = 4326 LIMIT 1"
>> parallel worker
>> LOCATION: GetLatestSnapshot, snapmgr.c:387
>
>I'm guessing ST_length is not parallel safe.
>
>What is your setting for?:
>
>max_parallel_workers_per_gather
>
>>
>>
>
>
>--
>Adrian Klaver
>adrian(dot)klaver(at)aklaver(dot)com

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Rene Romero Benavides 2019-03-14 06:15:17 Re: PostgreSQL temp table blues
Previous Message Noah Misch 2019-03-14 05:42:54 Re: LDAP authenticated session terminated by signal 11: Segmentation fault, PostgresSQL server terminates other active server processes