parallel query vs extensions

From: Jeff Janes <jeff(dot)janes(at)gmail(dot)com>
To: pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: parallel query vs extensions
Date: 2016-04-15 04:45:06
Message-ID: CAMkU=1yk6Kn7VM9b60H-m61q13vGKhwWrWFugrixqp17iBofkw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

I think there are a lot of extensions which create functions which
could benefit from being declared parallel safe. But how does one go
about doing that?

create extension xml2;
select xml_valid(filler),count(*) from pgbench_accounts group by 1;
Time: 3205.830 ms

alter function xml_valid (text) parallel safe;

select xml_valid(filler),count(*) from pgbench_accounts group by 1;
Time: 1803.936 ms

(Note that I have no particular interest in the xml2 extension, it
just provides a convenient demonstration of the general principle)

Should every relevant contrib extension get a version bump with a
transition file which is nothing but a list of "alter function blah
blah blah parallel safe" ?

And what of non-contrib extensions? Is there some clever alternative
to having a bunch of pseudo versions, like "1.0", "1.0_96", "1.1",
"1.1_9.6", "1.2", "1.2_96", etc.?

Cheers,

Jeff

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Fujii Masao 2016-04-15 05:03:08 Re: [COMMITTERS] pgsql: Add regression tests for multiple synchronous standbys.
Previous Message Kyotaro HORIGUCHI 2016-04-15 04:45:00 Re: Support for N synchronous standby servers - take 2