On 2013-06-11 12:53 CEST, Hannu Krosing wrote:
On 06/11/2013 10:47 AM, Andres Freund wrote:
On 2013-06-10 13:01:29 -0400, Andrew Dunstan wrote:
It's legal, is it not, to just write the equivalent Unicode character in
the JSON string and not use the escapes? If so I would think that that
would
On 2013-06-11 15:23 CEST, Hannu Krosing wrote:
On 06/11/2013 03:08 PM, Stefan Drees wrote:
...
What about this:
=# SELECT '{"measure":"seconds", "measure":42}'::json;
json
--
{"measure":
On 2013-11.06 17:28, Jon Nelson wrote:
There hasn't been much activity here recently. I'm curious, then, if
there are questions that I can answer.
It may be useful to summarize some things here:
- the purpose of the patch is to use posix_fallocate when creating new
WAL files, because it's (usua
On 2013-06-11 19:01 CEST, Hannu Krosing wrote:
On 06/11/2013 05:27 PM, Merlin Moncure wrote:
On Tue, Jun 11, 2013 at 9:45 AM, Stephen Frost ... wrote:
* Merlin Moncure ... wrote:
I agree with all your comments pretty much down the line. Need top
level CALL that supports parameterization and m
On 2013-06-11 19:45 CEST, Greg Smith wrote:
On 6/11/13 12:22 PM, Merlin Moncure wrote:
Personally I think this patch should go in regardless -- the concerns
made IMNSHO are specious.
That's nice, but we have this process for validating whether features go
in or not that relies on review inste
On 2013-06-15 08:44 CEST, Brendan Jurd wrote:
On 15 June 2013 16:18, Craig Ringer ... wrote:
On 06/15/2013 02:08 PM, Brendan Jurd wrote:
On 15 June 2013 14:43, Craig Ringer ... wrote:
The #1 question I see on Stack Overflow has to be confusion about
pg_hba.conf, mostly from people who have no
On 2013-06-17 16:41 +02:00, Kevin Grittner wrote:
Since there seems to be interest in discussing incremental
maintenance of materialized views *now*, I'm starting this thread
to try to avoid polluting unrelated threads with the discussion. I
don't intend to spend a lot of time on it until the CF
