Re: Socket communication for contrib - Mailing list pgsql-hackers

From Bob.Henkel@hartfordlife.com
Subject Re: Socket communication for contrib
Date
Msg-id OFF8924E70.89F1DEDA-ON86256E6D.0057EDFC-86256E6D.0057E887@hartfordlife.com
Whole thread Raw
In response to Socket communication for contrib  (Hans-Jürgen Schönig <postgres@cybertec.at>)
List pgsql-hackers




I would be FOR it if the README states the dangers



Bob Henkel          651-738-5085
Mutual Funds I/T Woodbury
Hartford Life
500 Bielenberg Drive
Woodbury, MN 55125


|---------+---------------------------->
|         |           Hans-Jürgen      |
|         |           Schönig          |
|         |           <postgres@cyberte|
|         |           c.at>            |
|         |                            |
|         |           04/05/2004 10:59 |
|         |           AM               |
|         |                            |
|---------+---------------------------->
>------------------------------------------------------------------------------------------------------------------------------|
|
     | |       To:       Tom Lane <tgl@sss.pgh.pa.us>
             | |       cc:       pgsql-hackers@postgresql.org, Bob.Henkel@hartfordlife.com
                     | |       Subject:  Re: [HACKERS] Socket communication for contrib
                             |
>------------------------------------------------------------------------------------------------------------------------------|




Tom Lane wrote:
> Hans-Jürgen Schönig <postgres@cybertec.at> writes:
>
>>Nested transactions: I don't think nested transactions will really help
>>to resolve the core problem. Committing a subtransaction will most
>>likely not imply that a parent transaction can be committed as well.
>
>
> Agreed.
>
>
>>As I said: Some people MIGHT find it useful in some special cases.
>>If the community decides that it does not enough sense to integrate it
>>into contrib I can live with that.
>
>
> I won't take a position on whether it's useful enough to put in contrib,
> but if people want it there, I'd just ask that the README be extended to
> point out the transactional risks.

this should not be a problem.
I can intregrate all necessary information there.

folks, let's do a poll ...
who is for it - who is against it ...
            regards,
                        Hans


--
Cybertec Geschwinde u Schoenig
Schoengrabern 134, A-2020 Hollabrunn, Austria
Tel: +43/2952/30706 or +43/664/233 90 75
www.cybertec.at, www.postgresql.at, kernel.cybertec.at








*************************************************************************
PRIVILEGED AND CONFIDENTIAL: This communication, including attachments, is for the exclusive use of addressee and may
containproprietary, confidential and/or privileged information.  If you are not the intended recipient, any use,
copying,disclosure, dissemination or distribution is strictly prohibited.  If you are not the intended recipient,
pleasenotify the sender immediately by return e-mail, delete this communication and destroy all copies. 
*************************************************************************



pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Socket communication for contrib
Next
From: Hans-Jürgen Schönig
Date:
Subject: Re: Socket communication for contrib