On Fri, Jan 27, 2012 at 2:56 PM, Pierre C li...@peufeu.com wrote:
Right. I think it makes more sense to try to get parallelism working
first with the infrastructure we have. Converting to use threading,
if we ever do it at all, should be something we view as a later
performance optimization.
Ok, thanks.
Att,
Fred
2012/1/24 Robert Haas robertmh...@gmail.com
On Tue, Jan 24, 2012 at 11:25 AM, Tom Lane t...@sss.pgh.pa.us wrote:
Robert Haas robertmh...@gmail.com writes:
I doubt it. Almost nothing in the backend is thread-safe. You can't
acquire a heavyweight lock, a
Not to mention palloc, another extremely fundamental and non-reentrant
subsystem.
Possibly we could work on making all that stuff re-entrant, but it would
be a huge amount of work for a distant and uncertain payoff.
Right. I think it makes more sense to try to get parallelism working
first
On Mon, Jan 23, 2012 at 2:45 PM, Merlin Moncure mmonc...@gmail.com wrote:
Yes, but OP is proposing to use multiple threads inside the forked
execution process. That's a completely different beast. Many other
databases support parallel execution of a single query and it might
very well be
Robert Haas robertmh...@gmail.com writes:
I doubt it. Almost nothing in the backend is thread-safe. You can't
acquire a heavyweight lock, a lightweight lock, or a spinlock. You
can't do anything that might elog() or ereport(). None of those
things are reentrant.
Not to mention palloc,
On Tue, Jan 24, 2012 at 11:25 AM, Tom Lane t...@sss.pgh.pa.us wrote:
Robert Haas robertmh...@gmail.com writes:
I doubt it. Almost nothing in the backend is thread-safe. You can't
acquire a heavyweight lock, a lightweight lock, or a spinlock. You
can't do anything that might elog() or
On 2012-01-13 21:14, Frederico wrote:
Hi folks.
Is there any restriction in create and start threads inside Postgres?
I'm trying to develop a multithread planner, and some times is raised a
exception of access memory.
I'm debugging the code to see if is a bug in the planner, but until now, I
On Fri, Jan 13, 2012 at 2:29 PM, Christopher Browne cbbro...@gmail.com wrote:
On Fri, Jan 13, 2012 at 3:14 PM, Frederico zepf...@gmail.com wrote:
Hi folks.
Is there any restriction in create and start threads inside Postgres?
I'm trying to develop a multithread planner, and some times is
This means it's possible use threads?
Att,
Fred
Enviado via iPad
Em 13/01/2012, às 20:47, Dimitri Fontaine dimi...@2ndquadrant.fr escreveu:
Christopher Browne cbbro...@gmail.com writes:
Yes, don't try to use threads.
Frederico zepf...@gmail.com writes:
This means it's possible use threads?
The short answer is “no”.
--
Dimitri Fontaine
http://2ndQuadrant.fr PostgreSQL : Expertise, Formation et Support
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your
On 13 January 2012 20:14, Frederico zepf...@gmail.com wrote:
I'm trying to develop a multithread planner, and some times is raised a
exception of access memory.
I was a bit confused about what you are trying to do -- somehow
use concurrency during the planning phase, or during
execution (maybe
Hi folks.
Is there any restriction in create and start threads inside Postgres?
I'm trying to develop a multithread planner, and some times is raised a
exception of access memory.
I'm debugging the code to see if is a bug in the planner, but until now, I
still not found. I tried to use the
On Fri, Jan 13, 2012 at 3:14 PM, Frederico zepf...@gmail.com wrote:
Hi folks.
Is there any restriction in create and start threads inside Postgres?
I'm trying to develop a multithread planner, and some times is raised a
exception of access memory.
I'm debugging the code to see if is a bug
Christopher Browne cbbro...@gmail.com writes:
Yes, don't try to use threads.
http://wiki.postgresql.org/wiki/Developer_FAQ#Why_don.27t_you_use_threads.2C_raw_devices.2C_async-I.2FO.2C_.3Cinsert_your_favorite_wizz-bang_feature_here.3E.3F
... threads are not currently used instead of multiple
14 matches
Mail list logo
