On 15 November 2013 21:03, Tom Lane t...@sss.pgh.pa.us wrote:
Thom Brown t...@linux.com writes:
Is this unintended, or is it something users should fix themselves by
being explicit about relation schemas in trigger functions? Should
the schema search path instead pick up whatever the default
On 11/15/2013 06:38 AM, Jaime Casanova wrote:
Please check for compiler warnings in pg_basebackup:
pg_basebackup.c:1109:1: warning: ‘escapeConnectionParameter’ defined but
not used [-Wunused-function]
pg_basebackup.c:1168:1: warning: ‘escape_quotes’ defined but not used
On Nov 15, 2013, at 12:37 PM, Andrew Dunstan and...@dunslane.net wrote:
It's making my head hurt, to be honest, and it sounds like a recipe for years
and years of inconsistencies and bugs.
I don't want to have two types, but I think I'd probably rather have two
clean types than this. I
On 11/15/2013 01:12 PM, David E. Wheeler wrote:
On Nov 15, 2013, at 12:37 PM, Andrew Dunstan and...@dunslane.net wrote:
It's making my head hurt, to be honest, and it sounds like a recipe for
years and years of inconsistencies and bugs.
I don't want to have two types, but I think I'd
Merlin Moncure-2 wrote
I don't want to have two types, but I think I'd probably rather have two
clean types than this. I can't imagine it being remotely acceptable to
have
behaviour depend in whether or not something was ever stored, which is
what
this looks like.
Well, maybe so. My main
On Fri, Nov 15, 2013 at 01:18:22PM -0800, Josh Berkus wrote:
I believe this was a danger we recognized when we added the JSON type,
including the possibility that a future binary type might need to be a
separate type due to compatibility issues. The only sad thing is the
naming; it would be
k...@rice.edu k...@rice.edu writes:
On Fri, Nov 15, 2013 at 01:18:22PM -0800, Josh Berkus wrote:
I believe this was a danger we recognized when we added the JSON type,
including the possibility that a future binary type might need to be a
separate type due to compatibility issues. The only
On 11/15/2013 04:53 PM, Tom Lane wrote:
k...@rice.edu k...@rice.edu writes:
On Fri, Nov 15, 2013 at 01:18:22PM -0800, Josh Berkus wrote:
I believe this was a danger we recognized when we added the JSON type,
including the possibility that a future binary type might need to be a
separate type
On Nov 15, 2013, at 2:02 PM, Andrew Dunstan and...@dunslane.net wrote:
Yeah, it would be a total foot gun here I think.
I've come to the conclusion that the only possible solution is to have a
separate type. That's a bit sad, but there it is. The upside is that this
will make the work
On 11/15/2013 11:49 AM, Marko Kreen wrote:
On Fri, Nov 15, 2013 at 11:16:25AM -0800, Adrian Klaver wrote:
The description of the GUCs show up in the documentation but I am
not seeing the GUCs themselves in postgresql.conf, so I could test
no further. It is entirely possible I am missing a step
On 11/15/2013 09:25 PM, Merlin Moncure wrote:
On Fri, Nov 15, 2013 at 1:51 PM, David E. Wheeler da...@justatheory.com
wrote:
On Nov 15, 2013, at 6:35 AM, Merlin Moncure mmonc...@gmail.com wrote:
Here are the options on the table:
1) convert existing json type to binary flavor
On Fri, Nov 15, 2013 at 4:31 PM, Hannu Krosing ha...@2ndquadrant.com wrote:
I think we need to take a *very* hard look at #3 before exploring #1
or #2: Haven't through it through yet but it may be possible to handle
this in such a way that will be mostly transparent to the end user and
may
David Rowley dgrowle...@gmail.com writes:
The tailing white space is fixed in the attached patch.
Applied with minor cosmetic adjustments.
regards, tom lane
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
On 11/15/2013 02:59 PM, Merlin Moncure wrote:
On Fri, Nov 15, 2013 at 4:31 PM, Hannu Krosing ha...@2ndquadrant.com wrote:
I think you may be on to something here. This might also be a way
opt-in to fast(er) serialization (upthread it was noted this is
unimportant; I'm skeptical). I deeply
On Mon, Oct 21, 2013 at 6:44 AM, Magnus Hagander mag...@hagander.net wrote:
+1. If changing at all, then maybe just autovacuum_mem?
I would like to stick with autovacuum_work_mem - it reflects the fact
that it's a setting shadowed by maintenance_work_mem, without being
too verbose.
--
Peter
On Fri, Nov 15, 2013 at 3:14 PM, Peter Eisentraut pete...@gmx.net wrote:
On 11/14/13, 4:35 PM, Christopher Browne wrote: On Thu, Nov 14, 2013 at
5:41 AM, Sameer Thakur samthaku...@gmail.com wrote:
So i think -g option is failing
Right you are.
I was missing a g: in the getopt_long() call.
Etsuro Fujita fujita.ets...@lab.ntt.co.jp writes:
I'd like to do the complementary explanation of this.
In tbm_union_page() and tbm_intersect_page() in tidbitmap.c, WORDS_PER_PAGE
is used in the scan of a lossy chunk, instead of WORDS_PER_CHUNK, where
these macros are defined as:
/* number
On Sat, Nov 16, 2013 at 4:09 AM, Alvaro Herrera alvhe...@2ndquadrant.comwrote:
David Rowley escribió:
On Fri, Nov 15, 2013 at 12:33 PM, Tomas Vondra t...@fuzzy.cz wrote:
Be careful with 'Name' data type - it's not just a simple string
buffer.
AFAIK it needs to work with hashing etc. so
Josh Berkus wrote
On 11/15/2013 02:59 PM, Merlin Moncure wrote:
On Fri, Nov 15, 2013 at 4:31 PM, Hannu Krosing lt;
hannu@
gt; wrote:
I think you may be on to something here. This might also be a way
opt-in to fast(er) serialization (upthread it was noted this is
unimportant; I'm
Looking at this a different way: could we just implement BSON and leave json
alone?
http://bsonspec.org/
David J.
--
View this message in context:
http://postgresql.1045698.n5.nabble.com/additional-json-functionality-tp5777975p5778656.html
Sent from the PostgreSQL - hackers mailing list
On 11/15/2013 04:00 PM, David Johnston wrote:
Looking at this a different way: could we just implement BSON and leave json
alone?
http://bsonspec.org/
In short? No.
For one thing, our storage format is different from theirs (better,
frankly), and as a result is not compliant with their
On 11/15/2013 07:32 PM, Josh Berkus wrote:
On 11/15/2013 04:00 PM, David Johnston wrote:
Looking at this a different way: could we just implement BSON and leave json
alone?
http://bsonspec.org/
In short? No.
For one thing, our storage format is different from theirs (better,
frankly), and
Sawada Masahiko sawada.m...@gmail.com writes:
I attached the patch which solves this problem, and have submitted to CF3.
I changed how to get the SQL from custom script file.
This needed a bit of work:
- Use of strncat didn't seem particularly safe, or efficient. I changed
it to explicitly
On Sun, Oct 20, 2013 at 7:21 AM, Magnus Hagander mag...@hagander.net wrote:
On Sun, Oct 20, 2013 at 2:22 AM, Peter Geoghegan p...@heroku.com wrote:
It seemed neater to me to create a new flag, so that in principle any
vacuum() code path can request autovacuum_work_mem, rather than having
On Wed, Nov 13, 2013 at 9:37 PM, Josh Berkus j...@agliodbs.com wrote:
handyrep@john:~/handyrep$ pg_isready --version
pg_isready (PostgreSQL) 9.3.1
handyrep@john:~/handyrep$ pg_isready -h john -p 5432 -U postgres -d
postgres -q
pg_isready: missing = after postgres in connection info string
On Fri, 2013-11-15 at 13:01 -0500, Andrew Dunstan wrote:
Attached is a patch to provide a new event trigger that will fire on
transaction commit.
xact.c: In function ‘CommitTransaction’:
xact.c:1835:3: warning: implicit declaration of function
‘PreCommitTriggersFire’
On 11/15/2013 09:07 PM, Peter Eisentraut wrote:
On Fri, 2013-11-15 at 13:01 -0500, Andrew Dunstan wrote:
Attached is a patch to provide a new event trigger that will fire on
transaction commit.
xact.c: In function ‘CommitTransaction’:
xact.c:1835:3: warning: implicit declaration of function
On Fri, Nov 15, 2013 at 10:18 PM, Peter Eisentraut pete...@gmx.net wrote:
On 11/14/13, 2:50 AM, Amit Kapila wrote:
Find the rebased version attached with this mail.
Doesn't build:
openjade -wall -wno-unused-param -wno-empty -wfully-tagged -D . -D . -c
On 15 November 2013 17:26 Magnus Hagander wrote:
On Fri, Nov 15, 2013 at 12:10 PM, Haribabu kommi
haribabu.ko...@huawei.commailto:haribabu.ko...@huawei.com wrote:
On 14 November 2013 23:59 Fujii Masao wrote:
On Thu, Nov 14, 2013 at 9:08 PM, Haribabu kommi
on 15 November 2013 17:26 Magnus Hagander wrote:
On Fri, Nov 15, 2013 at 12:10 PM, Haribabu kommi
haribabu.ko...@huawei.commailto:haribabu.ko...@huawei.com wrote:
On 14 November 2013 23:59 Fujii Masao wrote:
On Thu, Nov 14, 2013 at 9:08 PM, Haribabu kommi
101 - 130 of 130 matches
Mail list logo