Re: Parallel safety tagging of extension functions - Mailing list pgsql-hackers

From Andreas Karlsson
Subject Re: Parallel safety tagging of extension functions
Date
Msg-id 575222DA.1030109@proxel.se
Whole thread Raw
In response to Re: Parallel safety tagging of extension functions  (Robert Haas <robertmhaas@gmail.com>)
Responses Re: Parallel safety tagging of extension functions
List pgsql-hackers
Hi,

Here is the patch split into many small patches as you suggested. The
current patches are based on top of the patch which fixes the signatures
for gin and gist functions.

These patches only touch functions which never should be called
directly, so they are fine to skip. I decided to attach them anyway in
case you fell like applying them.

parallel-contrib-v2-bloom.patch.gz
parallel-contrib-v2-btree_gin.patch.gz
parallel-contrib-v2-btree_gist.patch.gz
parallel-contrib-v2-dict_int.patch.gz
parallel-contrib-v2-dict_xsyn.patch.gz
parallel-contrib-v2-file_fdw.patch.gz
parallel-contrib-v2-hstore_plperl.patch.gz
parallel-contrib-v2-hstore_plpython.patch.gz
parallel-contrib-v2-ltree_plpython.patch.gz
parallel-contrib-v2-postgres_fdw.patch.gz
parallel-contrib-v2-tsm_system_rows.patch.gz
parallel-contrib-v2-tsm_system_time.patch.gz

These two mostly concern triggers so i guess they could be skipped too.

parallel-contrib-v2-tcn.patch.gz
parallel-contrib-v2-spi.patch.gz

Andreas

Attachment

pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Number of parentheses in check constraints affected by operator_precedence_warning
Next
From: Noah Misch
Date:
Subject: Re: Perf Benchmarking and regression.