? I still could be
wrong with -hackers, so just let me know where to go with this if I'm still
off-base.
-Ryan Kelly
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
On Mon, Jan 09, 2012 at 10:35:50AM +0200, Heikki Linnakangas wrote:
On 08.01.2012 22:18, Ryan Kelly wrote:
@@ -1570,7 +1570,13 @@ do_connect(char *dbname, char *user, char *host, char
*port)
keywords[7] = NULL;
values[7] = NULL;
-n_conn
On Tue, Jan 10, 2012 at 11:29:58AM +0200, Heikki Linnakangas wrote:
On 09.01.2012 15:49, Ryan Kelly wrote:
On Mon, Jan 09, 2012 at 10:35:50AM +0200, Heikki Linnakangas wrote:
That assumes that it's safe to longjmp out of PQconnectdbParams at
any instant. It's not.
I'm guessing because
On Mon, Jul 09, 2012 at 05:35:15PM +0900, Shigeru HANADA wrote:
Hi Ryan,
On Mon, Jun 25, 2012 at 9:00 PM, Ryan Kelly rpkell...@gmail.com wrote:
Connection attempt by \connect command could be also canceled by
pressing Ctrl+C on psql prompt.
In addition, I tried setting
against latest
HEAD attached.
--
Álvaro Herrera alvhe...@commandprompt.com
The PostgreSQL Company - Command Prompt, Inc.
PostgreSQL Replication, Consulting, Custom Development, 24x7 support
-Ryan Kelly
diff --git a/doc/src/sgml/libpq.sgml b/doc/src/sgml/libpq.sgml
index 8a820ac..bf4d110
that came with my release :)
-Ryan Kelly
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
/manual/html_node/Compression-algorithms-used-in-the-record-layer.html
http://www.openssl.org/docs/apps/enc.html
-Ryan Kelly
--
Magnus Hagander
Me: http://www.hagander.net/
Work: http://www.redpill-linpro.com/
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make
I had trouble finding what operators arrays supported or which ones
had index support or even determining that arrays could be indexed from
the documentation from the array data type. So, patch.
-Ryan Kelly
diff --git a/doc/src/sgml/array.sgml b/doc/src/sgml/array.sgml
index 3508ba3..51d996d
Shigeru:
Thank you very much for your review. Comments are inline below, and a
new patch is attached.
On Fri, Jun 22, 2012 at 10:06:53AM +0900, Shigeru HANADA wrote:
(2012/05/01 0:30), Ryan Kelly wrote:
On Mon, Apr 30, 2012 at 09:02:33AM -0400, Alvaro Herrera wrote:
Well, do *you* want
subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
-Ryan Kelly
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
On Wed, May 05/08/13, 2013 at 10:55:40AM -0700, David Fetter wrote:
On Wed, May 08, 2013 at 01:16:14PM -0400, Tom Lane wrote:
Heikki Linnakangas hlinnakan...@vmware.com writes:
On 08.05.2013 19:44, Tom Lane wrote:
No there isn't; what you suggest would require FE/BE protocol
On Wed, May 05/08/13, 2013 at 03:38:10PM -0400, Andrew Dunstan wrote:
On 05/08/2013 03:23 PM, Jim Nasby wrote:
WITH new_data AS (
COPY FROM ...
RETURNING id, field_to_check
)
Why is this better than this, which you can do today?
WITH new_data AS (
INSERT into ...
I submitted essentially this same patch over a year ago and Tom vetoed
it: http://www.postgresql.org/message-id/3741.1325731...@sss.pgh.pa.us
The thread moved to -hackers at some point and I made some further
enhancements:
On Wed, Aug 08/07/13, 2013 at 07:29:32PM -0400, Hannu Krosing wrote:
Has anybody been able to install Pg 9.3 beta .debs on Ubuntu 12.04
Yes.
when I try to select postgresql-9.3 (9,3~beta2-2.pgdg12.4+1) for
installation I get error saying
...
The following packages have unmet dependencies:
' as example from test;
^
LOCATION: LookupTypeName, parse_type.c:171
-Ryan Kelly
missing_type_schema_hint.patch
Description: Binary data
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref
On Tue, Feb 3, 2015 at 11:10 AM, Tom Lane t...@sss.pgh.pa.us wrote:
Ryan Kelly rpkell...@gmail.com writes:
The attached patch adds a LINE: ... hint when schemaname.typename
results in a schema which does not exist. I came across this when a
missing comma in a SELECT list resulted in an error
16 matches
Mail list logo
