Re: Threading in BGWorkers (!) - Mailing list pgsql-hackers

From James Sewell
Subject Re: Threading in BGWorkers (!)
Date
Msg-id CAANVwEsx35ar0c3A1nq2DbgnW5K+58t_Hfpd2Fr1kRFWZGq0mw@mail.gmail.com
Whole thread Raw
In response to Re: Threading in BGWorkers (!)  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
We need some kind of concrete plan for what is a
usable amount of functionality and what has to be done to get it.

This is exactly the type of discussion I'm after. 

I'll start.

A usable amount of functionality would be the ability to start threads from:
  • a background worker
These cases should be bound by *at least* the following rules:
  • no signal handling from threads
  • no calls into PostgreSQL functions from threads

The patch I supplied is one of the requirements to get there - I would love help to discover the others.


The contents of this email are confidential and may be subject to legal or professional privilege and copyright. No representation is made that this email is free of viruses or other defects. If you have received this communication in error, you may not copy or distribute any part of it or otherwise disclose its contents to anyone. Please advise the sender of your incorrect receipt of this correspondence.

pgsql-hackers by date:

Previous
From: "movead.li@highgo.ca"
Date:
Subject: Re: POC and rebased patch for CSN based snapshots
Next
From: Hamid Akhtar
Date:
Subject: Re: Rethinking opclass member checks and dependency strength