Re: COPYable logs status

From: Markus Schiltknecht <markus(at)bluegap(dot)ch>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: "Matthew T(dot) O'Connor" <matthew(at)zeut(dot)net>, Andrew Dunstan <andrew(at)dunslane(dot)net>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: COPYable logs status
Date: 2007-06-09 14:57:27
Message-ID: 466ABFD7.9060302@bluegap.ch
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers pgsql-patches

Tom Lane wrote:
> Markus Schiltknecht <markus(at)bluegap(dot)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?

I was refering to the 'getting data to another process' problem. If
that's the problem (as you said upthread) imessages might be a solution.

> Trapping what comes out of stderr is simply too useful a behavior to lose.

Sure. I've never said anything against that.

Regards

Markus

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Teodor Sigaev 2007-06-09 15:03:15 Re: Tsearch vs Snowball, or what's a source file?
Previous Message Tom Lane 2007-06-09 14:22:04 Re: Issues with factorial operator

Browse pgsql-patches by date

  From Date Subject
Next Message Gregory Stark 2007-06-09 19:12:07 Re: Synchronized scans
Previous Message Tom Lane 2007-06-09 13:58:43 Re: Synchronized scans