Re: COPYable logs status - Mailing list pgsql-hackers

From Tom Lane
Subject Re: COPYable logs status
Date
Msg-id 15557.1181396801@sss.pgh.pa.us
Whole thread Raw
In response to Re: COPYable logs status  (Markus Schiltknecht <markus@bluegap.ch>)
Responses Re: COPYable logs status
List pgsql-hackers
Markus Schiltknecht <markus@bluegap.ch> writes:
> Tom Lane wrote:
>> We *have* a log-writing process.  The problem is in getting the data to it.

> Remember the imessages approach I'm using for Postgres-R? It passes 
> messages around using shared memory and signals the receiver on incoming 
> data. It's not perfect, sure, but it's a general solution to a common 
> problem.

Uh-huh.  And how will you get libc's dynamic-link code to buy into
issuing link error messages this way?  Not to mention every other bit
of code that might get linked into the backend?

Trapping what comes out of stderr is simply too useful a behavior to lose.
        regards, tom lane


pgsql-hackers by date:

Previous
From: Lukas Kahwe Smith
Date:
Subject: Re: Using the GPU
Next
From: Tom Lane
Date:
Subject: Re: COPYable logs status