From noreply at pgfoundry.org Sat Feb 2 16:43:38 2008 From: noreply at pgfoundry.org (noreply at pgfoundry.org) Date: Sat, 2 Feb 2008 16:43:38 +0000 (UTC) Subject: [ python-Bugs-1010222 ] Validate order of messages Message-ID: <20080202164339.00D2617AD11D@pgfoundry.org> Bugs item #1010222, was opened at 2008-01-05 22:39 You can respond by visiting: http://pgfoundry.org/tracker/?func=detail&atid=442&aid=1010222&group_id=1000094 Category: pq/pqueue Group: None Status: Open >Resolution: Accepted Priority: 3 Submitted By: James Pye (jwp) Assigned to: James Pye (jwp) Summary: Validate order of messages Initial Comment: Currently, the client3.Transaction class will not *always* check to make sure messages come in order. Rather, in many situations it merely compares the incoming message to a set of messages. If it's contained in the set it sees it as "Ok", which is wrong. Usually, this does not cause problems, but it does keep the driver from identifying bad backends. ---------------------------------------------------------------------- >Comment By: James Pye (jwp) Date: 2008-02-02 09:43 Message: This is being fixed by changing the structure of the "hook" attribute. hook is now a mapping of client requests to a sequence of response steps. Each step is a dictionary of receivable messages associated with the message parser and the next step pointer. If the next step is None, the response is complete. The position of the transaction will have two new items in the tuple: last step and current step. Last step points to the starting position of the last set of messages processed. Current step points at the position to be used for the next sequence of messages. ---------------------------------------------------------------------- You can respond by visiting: http://pgfoundry.org/tracker/?func=detail&atid=442&aid=1010222&group_id=1000094 From noreply at pgfoundry.org Sat Feb 2 16:44:01 2008 From: noreply at pgfoundry.org (noreply at pgfoundry.org) Date: Sat, 2 Feb 2008 16:44:01 +0000 (UTC) Subject: [ python-Bugs-1010222 ] Validate order of messages Message-ID: <20080202164401.7F01B17AD13D@pgfoundry.org> Bugs item #1010222, was opened at 2008-01-05 22:39 You can respond by visiting: http://pgfoundry.org/tracker/?func=detail&atid=442&aid=1010222&group_id=1000094 Category: pq/pqueue Group: None Status: Open Resolution: Accepted Priority: 3 Submitted By: James Pye (jwp) Assigned to: James Pye (jwp) Summary: Validate order of messages Initial Comment: Currently, the client3.Transaction class will not *always* check to make sure messages come in order. Rather, in many situations it merely compares the incoming message to a set of messages. If it's contained in the set it sees it as "Ok", which is wrong. Usually, this does not cause problems, but it does keep the driver from identifying bad backends. ---------------------------------------------------------------------- Comment By: James Pye (jwp) Date: 2008-02-02 09:43 Message: This is being fixed by changing the structure of the "hook" attribute. hook is now a mapping of client requests to a sequence of response steps. Each step is a dictionary of receivable messages associated with the message parser and the next step pointer. If the next step is None, the response is complete. The position of the transaction will have two new items in the tuple: last step and current step. Last step points to the starting position of the last set of messages processed. Current step points at the position to be used for the next sequence of messages. ---------------------------------------------------------------------- You can respond by visiting: http://pgfoundry.org/tracker/?func=detail&atid=442&aid=1010222&group_id=1000094 From noreply at pgfoundry.org Sat Feb 2 21:52:03 2008 From: noreply at pgfoundry.org (noreply at pgfoundry.org) Date: Sat, 2 Feb 2008 21:52:03 +0000 (UTC) Subject: [ python-Bugs-1010222 ] Validate order of messages Message-ID: <20080202215203.DC62A17AD134@pgfoundry.org> Bugs item #1010222, was opened at 2008-01-05 22:39 You can respond by visiting: http://pgfoundry.org/tracker/?func=detail&atid=442&aid=1010222&group_id=1000094 Category: pq/pqueue Group: None >Status: Closed Resolution: Accepted Priority: 3 Submitted By: James Pye (jwp) Assigned to: James Pye (jwp) Summary: Validate order of messages Initial Comment: Currently, the client3.Transaction class will not *always* check to make sure messages come in order. Rather, in many situations it merely compares the incoming message to a set of messages. If it's contained in the set it sees it as "Ok", which is wrong. Usually, this does not cause problems, but it does keep the driver from identifying bad backends. ---------------------------------------------------------------------- >Comment By: James Pye (jwp) Date: 2008-02-02 14:52 Message: Done. =) Quite a win, actually. Ended up being easier than I expected, and no tangible loss of performance. ---------------------------------------------------------------------- Comment By: James Pye (jwp) Date: 2008-02-02 09:43 Message: This is being fixed by changing the structure of the "hook" attribute. hook is now a mapping of client requests to a sequence of response steps. Each step is a dictionary of receivable messages associated with the message parser and the next step pointer. If the next step is None, the response is complete. The position of the transaction will have two new items in the tuple: last step and current step. Last step points to the starting position of the last set of messages processed. Current step points at the position to be used for the next sequence of messages. ---------------------------------------------------------------------- You can respond by visiting: http://pgfoundry.org/tracker/?func=detail&atid=442&aid=1010222&group_id=1000094 From noreply at pgfoundry.org Sat Feb 2 21:53:23 2008 From: noreply at pgfoundry.org (noreply at pgfoundry.org) Date: Sat, 2 Feb 2008 21:53:23 +0000 (UTC) Subject: [ python-Bugs-1010263 ] Add split_statement to postgresql.strings Message-ID: <20080202215323.908F317AD134@pgfoundry.org> Bugs item #1010263, was opened at 2008-02-02 14:53 You can respond by visiting: http://pgfoundry.org/tracker/?func=detail&atid=442&aid=1010263&group_id=1000094 Category: lo/foundation Group: To do Status: Open Resolution: None Priority: 4 Submitted By: James Pye (jwp) Assigned to: James Pye (jwp) Summary: Add split_statement to postgresql.strings Initial Comment: Use the split function to safely scan for semicolons in a given string. ---------------------------------------------------------------------- You can respond by visiting: http://pgfoundry.org/tracker/?func=detail&atid=442&aid=1010263&group_id=1000094 From noreply at pgfoundry.org Sun Feb 3 00:45:58 2008 From: noreply at pgfoundry.org (noreply at pgfoundry.org) Date: Sun, 3 Feb 2008 00:45:58 +0000 (UTC) Subject: [ python-Bugs-1010250 ] Correct ctl freezes Message-ID: <20080203004558.0B07117AD134@pgfoundry.org> Bugs item #1010250, was opened at 2008-01-24 20:16 You can respond by visiting: http://pgfoundry.org/tracker/?func=detail&atid=442&aid=1010250&group_id=1000094 Category: None Group: None Status: Open Resolution: None Priority: 3 Submitted By: James Pye (jwp) >Assigned to: James Pye (jwp) Summary: Correct ctl freezes Initial Comment: Sometimes pg_ctl and initdb will freeze. This is likely due to some blocked writes for some reason. Further investigation is needed. ---------------------------------------------------------------------- You can respond by visiting: http://pgfoundry.org/tracker/?func=detail&atid=442&aid=1010250&group_id=1000094 From noreply at pgfoundry.org Sun Feb 3 00:50:38 2008 From: noreply at pgfoundry.org (noreply at pgfoundry.org) Date: Sun, 3 Feb 2008 00:50:38 +0000 (UTC) Subject: [ python-Bugs-1010253 ] Fix DB-API parameter substitution Message-ID: <20080203005038.6320617AD134@pgfoundry.org> Bugs item #1010253, was opened at 2008-01-27 14:49 You can respond by visiting: http://pgfoundry.org/tracker/?func=detail&atid=442&aid=1010253&group_id=1000094 Category: fe/proboscis Group: None Status: Open Resolution: None Priority: 3 Submitted By: James Pye (jwp) Assigned to: James Pye (jwp) Summary: Fix DB-API parameter substitution Initial Comment: Currently the DB-API layer stupidly substitutes '?' for $n. This can cause issues if a question-mark is placed in a quoted section. Additionally, switch the paramstyle to named parameters to sync up with psycopg2. This depends on the strings module being added to pg_foundation. ---------------------------------------------------------------------- >Comment By: James Pye (jwp) Date: 2008-02-02 17:50 Message: strings module has been added to pg_foundation-1.0dev(HEAD). Small matter of code. An alteration, however. Make the paramstyle consistent with psycopg2's. Considering that psyco is undoubtably the most popular driver available, try to make the dbapi2 module compatible with it. ---------------------------------------------------------------------- You can respond by visiting: http://pgfoundry.org/tracker/?func=detail&atid=442&aid=1010253&group_id=1000094 From noreply at pgfoundry.org Sun Feb 3 19:52:41 2008 From: noreply at pgfoundry.org (noreply at pgfoundry.org) Date: Sun, 3 Feb 2008 19:52:41 +0000 (UTC) Subject: [ python-Bugs-1010246 ] Prepared transaction interfaces Message-ID: <20080203195241.A8FA317ADCC4@pgfoundry.org> Bugs item #1010246, was opened at 2008-01-18 15:47 You can respond by visiting: http://pgfoundry.org/tracker/?func=detail&atid=442&aid=1010246&group_id=1000094 Category: fe/proboscis Group: None >Status: Closed >Resolution: Accepted Priority: 3 Submitted By: James Pye (jwp) Assigned to: James Pye (jwp) Summary: Prepared transaction interfaces Initial Comment: Two interfaces need to be described. Initial preparation and final commit. Initial prepare can be handled by the regular transaction manager: with gtx.xact('gid'): ... In which case, the usual COMMIT is replaced with a PREPARE TRANSACTION 'gid'. Additionally, an interface needs to be developed for committing a set of transactions. ---------------------------------------------------------------------- >Comment By: James Pye (jwp) Date: 2008-02-03 12:52 Message: The xact's gid is now configurable. I'll open another bug for creating a set manager. ---------------------------------------------------------------------- You can respond by visiting: http://pgfoundry.org/tracker/?func=detail&atid=442&aid=1010246&group_id=1000094 From noreply at pgfoundry.org Sun Feb 3 20:55:21 2008 From: noreply at pgfoundry.org (noreply at pgfoundry.org) Date: Sun, 3 Feb 2008 20:55:21 +0000 (UTC) Subject: [ python-Bugs-1010237 ] Implement __nonzero__ in tracenull.GreenTrunk_Connection Message-ID: <20080203205521.8C86917AD135@pgfoundry.org> Bugs item #1010237, was opened at 2008-01-14 19:12 You can respond by visiting: http://pgfoundry.org/tracker/?func=detail&atid=442&aid=1010237&group_id=1000094 Category: fe/proboscis Group: None >Status: Closed >Resolution: Accepted Priority: 3 Submitted By: James Pye (jwp) Assigned to: James Pye (jwp) Summary: Implement __nonzero__ in tracenull.GreenTrunk_Connection Initial Comment: Add a nonzero method that allows a user to identify a connection that can process a query without causing a known exception. So self.state not in ('E', 'LOST', None) and not self.closed. ---------------------------------------------------------------------- >Comment By: James Pye (jwp) Date: 2008-02-03 13:55 Message: Also added __nonzero__ to greentrunk connection API. ---------------------------------------------------------------------- You can respond by visiting: http://pgfoundry.org/tracker/?func=detail&atid=442&aid=1010237&group_id=1000094 From noreply at pgfoundry.org Sun Feb 3 21:12:21 2008 From: noreply at pgfoundry.org (noreply at pgfoundry.org) Date: Sun, 3 Feb 2008 21:12:21 +0000 (UTC) Subject: [ python-Bugs-1010264 ] Implement a queue for protocol transactions Message-ID: <20080203211221.4963217AD135@pgfoundry.org> Bugs item #1010264, was opened at 2008-02-03 14:12 You can respond by visiting: http://pgfoundry.org/tracker/?func=detail&atid=442&aid=1010264&group_id=1000094 Category: fe/proboscis Group: To do Status: Open Resolution: None Priority: 5 Submitted By: James Pye (jwp) Assigned to: James Pye (jwp) Summary: Implement a queue for protocol transactions Initial Comment: Currently, only one transaction can be set for processing. However, some situations involving transactions can benefit substantially from queueing the transactions to avoid extra round-trips. Granted, any kind of commit does not have this luxury, but starts and rollbacks can certainly benefit from this. This would allow request messages of a sequences of protocol transactions to be sent out in one write. Removing any need or desire to combine multiple requests into a single transaction. ---------------------------------------------------------------------- You can respond by visiting: http://pgfoundry.org/tracker/?func=detail&atid=442&aid=1010264&group_id=1000094 From noreply at pgfoundry.org Sun Feb 3 21:59:58 2008 From: noreply at pgfoundry.org (noreply at pgfoundry.org) Date: Sun, 3 Feb 2008 21:59:58 +0000 (UTC) Subject: [ python-Bugs-1010263 ] Add split_statement to postgresql.strings Message-ID: <20080203215958.A000D17AD135@pgfoundry.org> Bugs item #1010263, was opened at 2008-02-02 14:53 You can respond by visiting: http://pgfoundry.org/tracker/?func=detail&atid=442&aid=1010263&group_id=1000094 Category: lo/foundation Group: To do >Status: Closed >Resolution: Accepted Priority: 4 Submitted By: James Pye (jwp) Assigned to: James Pye (jwp) Summary: Add split_statement to postgresql.strings Initial Comment: Use the split function to safely scan for semicolons in a given string. ---------------------------------------------------------------------- >Comment By: James Pye (jwp) Date: 2008-02-03 14:59 Message: split_sql and split_sql_str are the new functions. ---------------------------------------------------------------------- You can respond by visiting: http://pgfoundry.org/tracker/?func=detail&atid=442&aid=1010263&group_id=1000094 From noreply at pgfoundry.org Mon Feb 4 01:40:14 2008 From: noreply at pgfoundry.org (noreply at pgfoundry.org) Date: Mon, 4 Feb 2008 01:40:14 +0000 (UTC) Subject: [ python-Bugs-1010265 ] Automatically add self-signed certs Message-ID: <20080204014014.E1B7D17AD13D@pgfoundry.org> Bugs item #1010265, was opened at 2008-02-03 18:40 You can respond by visiting: http://pgfoundry.org/tracker/?func=detail&atid=442&aid=1010265&group_id=1000094 Category: tin/tin Group: To do Status: Open Resolution: None Priority: 3 Submitted By: James Pye (jwp) Assigned to: James Pye (jwp) Summary: Automatically add self-signed certs Initial Comment: When clusters are initialized, if the installation of PostgreSQL supports SSL, generate the server.key and server.crt files for using SSL. Also, generate the corresponding client files as well for 8.3 and greater. ---------------------------------------------------------------------- You can respond by visiting: http://pgfoundry.org/tracker/?func=detail&atid=442&aid=1010265&group_id=1000094 From noreply at pgfoundry.org Mon Feb 4 02:10:31 2008 From: noreply at pgfoundry.org (noreply at pgfoundry.org) Date: Mon, 4 Feb 2008 02:10:31 +0000 (UTC) Subject: [ python-Bugs-1010266 ] Add ldap support to pg_service.conf Message-ID: <20080204021031.816D617AC904@pgfoundry.org> Bugs item #1010266, was opened at 2008-02-03 19:10 You can respond by visiting: http://pgfoundry.org/tracker/?func=detail&atid=442&aid=1010266&group_id=1000094 Category: lo/foundation Group: To do Status: Open Resolution: None Priority: 3 Submitted By: James Pye (jwp) Assigned to: James Pye (jwp) Summary: Add ldap support to pg_service.conf Initial Comment: 8.3 added the ability to lookup connection parameters using LDAP with libpq. Do the same in utility.client.option and utility.client.environ. http://www.postgresql.org/docs/8.3/static/libpq-ldap.html http://python-ldap.sourceforge.net/ ---------------------------------------------------------------------- You can respond by visiting: http://pgfoundry.org/tracker/?func=detail&atid=442&aid=1010266&group_id=1000094 From noreply at pgfoundry.org Mon Feb 4 02:14:05 2008 From: noreply at pgfoundry.org (noreply at pgfoundry.org) Date: Mon, 4 Feb 2008 02:14:05 +0000 (UTC) Subject: [ python-Bugs-1010238 ] SSL support Message-ID: <20080204021406.0AFC417AC904@pgfoundry.org> Bugs item #1010238, was opened at 2008-01-15 20:47 You can respond by visiting: http://pgfoundry.org/tracker/?func=detail&atid=442&aid=1010238&group_id=1000094 Category: fe/proboscis Group: To do Status: Open Resolution: None Priority: 4 Submitted By: James Pye (jwp) Assigned to: James Pye (jwp) Summary: SSL support Initial Comment: The logic is there, but it does not appear to work very well. Fix the sslmode support, and implement usage of the ssl module that appears in 2.6. PostgreSQL 8.3 has support for checking certificates; be sure to add this as well; the ssl module does have the necessary facilities to accomplish this. ---------------------------------------------------------------------- >Comment By: James Pye (jwp) Date: 2008-02-03 19:14 Message: Made some headway here. Still need to use the keyfile and certfile parameters with the ssl.wrap_socket().. ---------------------------------------------------------------------- You can respond by visiting: http://pgfoundry.org/tracker/?func=detail&atid=442&aid=1010238&group_id=1000094 From noreply at pgfoundry.org Tue Feb 5 01:47:03 2008 From: noreply at pgfoundry.org (noreply at pgfoundry.org) Date: Tue, 5 Feb 2008 01:47:03 +0000 (UTC) Subject: [ python-Bugs-1010238 ] SSL support Message-ID: <20080205014703.F160817AD0A2@pgfoundry.org> Bugs item #1010238, was opened at 2008-01-15 20:47 You can respond by visiting: http://pgfoundry.org/tracker/?func=detail&atid=442&aid=1010238&group_id=1000094 Category: fe/proboscis Group: To do Status: Open Resolution: None Priority: 4 Submitted By: James Pye (jwp) Assigned to: James Pye (jwp) Summary: SSL support Initial Comment: The logic is there, but it does not appear to work very well. Fix the sslmode support, and implement usage of the ssl module that appears in 2.6. PostgreSQL 8.3 has support for checking certificates; be sure to add this as well; the ssl module does have the necessary facilities to accomplish this. ---------------------------------------------------------------------- >Comment By: James Pye (jwp) Date: 2008-02-04 18:47 Message: This is checked into HEAD(1.0dev) now, and appears to work. However, only the basic aspect of this has been manually tested. So, for this bug to be closed, proboscis will need automated tests, and revocation support. pg_tin can help with the automated tests. There's already a bug readied for it to add support for initializing the certificate files. ---------------------------------------------------------------------- Comment By: James Pye (jwp) Date: 2008-02-03 19:14 Message: Made some headway here. Still need to use the keyfile and certfile parameters with the ssl.wrap_socket().. ---------------------------------------------------------------------- You can respond by visiting: http://pgfoundry.org/tracker/?func=detail&atid=442&aid=1010238&group_id=1000094