For some reason, or possibly just through my carelessness and for no
real reason, json_object() currently disallows empty strings as object
keys. However silly empty string keys might be, they are apparently
allowed by the JSON rfcs, and this behaviour by json_object() is
inconsistent with
On 07/21/2014 02:40 PM, Tom Lane wrote:
Robert Haas robertmh...@gmail.com writes:
Mmph. Well, I don't want to install a non-default Perl on my system
just to make these tests pass, and I don't think that should be a
requirement.
I had the same feeling about the Perl on RHEL6 ;-). The TAP
I have just noticed that I inadvertently marked the json_build*
functions as immutable. That seems to be a plain error, as, for example,
timestamptz output will not be immutable. I think we need to fix this
for 9.4. It will mean a catalog bump :-(
cheers
andrew
--
Sent via pgsql-hackers
On 07/15/2014 11:14 AM, Tom Lane wrote:
I think we need to fix this
for 9.4. It will mean a catalog bump :-(
Agreed.
Are we trying to store these up or just applying them as they go?
cheers
andrew
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to
On 07/14/2014 03:44 PM, Robert Haas wrote:
populate_record_worker in jsonfuncs.c says this:
if (get_call_result_type(fcinfo, NULL, tupdesc) != TYPEFUNC_COMPOSITE)
ereport(ERROR,
(errcode(ERRCODE_FEATURE_NOT_SUPPORTED),
On 07/14/2014 04:46 PM, Robert Haas wrote:
On Mon, Jul 14, 2014 at 4:39 PM, Andrew Dunstan and...@dunslane.net wrote:
Is there any reasonable alternative? That is, if you have a function
returning SETOF record, and the details of the record type aren't
specified, is there anything you can do
On 07/02/2014 05:08 AM, Torsten Zuehlsdorff wrote:
Hello,
i've tried to setup a FreeBSD 10 machine as buildfarm-member. But it's
an IPv6 only machine and there is no IPv6 for the homepage.
Can anyone add support for IPv6 to it?
I'm looking into this.
cheers
andrew
--
Sent via
I've always been a bit reluctant to accept buildfarm members that are
constantly being updated, because it seemed to me that it created
something with too many variables. However, we occasionally get requests
from people who want to run on such platforms, and I'm also a bit
reluctant to turn
On 06/25/2014 02:46 PM, Tom Lane wrote:
Why do we have essentially duplicate pg_proc entries for json_extract_path
and json_extract_path_op? The latter is undocumented and seems only to be
used as the infrastructure for the # operator. I see that only the
former is marked variadic, but AFAIK
On 06/26/2014 03:11 PM, Tom Lane wrote:
Andrew Dunstan and...@dunslane.net writes:
On 06/25/2014 02:46 PM, Tom Lane wrote:
Why do we have essentially duplicate pg_proc entries for json_extract_path
and json_extract_path_op?
Likewise for json_extract_path_text_op, jsonb_extract_path_op
On 06/23/2014 09:43 PM, Tom Lane wrote:
Andrew Dunstan and...@dunslane.net writes:
On 06/23/2014 07:34 PM, Tom Lane wrote:
I'm not following your comment about 9.3. The json[b]_to_record[set]
functions are new in 9.4, which is what makes me feel it's not too
late to redefine their behavior
On 06/23/2014 10:51 AM, rohtodeveloper wrote:
Dear all，
Our application will be switched from SQL Server to PostgreSQL.
However, a few functions are not supported yet. So we decided to
extend it.
The functions are as following:
1.SQL statement support
INSERT statement without INTO keyword
On 06/23/2014 11:06 AM, Robert Haas wrote:
On Fri, Jun 20, 2014 at 11:26 AM, Joey Caughey
jcaug...@parrotmarketing.com wrote:
I’m having an issue with JSON requests in Postgres and was wondering if
anyone had an answer.
I have an orders table with a field called “json_data”.
In the json data
On 06/23/2014 11:43 AM, Tom Lane wrote:
Michael Paquier michael.paqu...@gmail.com writes:
Digging more into that, I have found the issue and a fix for it. It happens
that populate_recordset_object_start, which is used to initialize the
process for the population of the record, is taken *each*
On 06/23/2014 07:34 PM, Tom Lane wrote:
Andrew Dunstan and...@dunslane.net writes:
On 06/23/2014 11:43 AM, Tom Lane wrote:
However, it seems to me that these functions (json[b]_to_record[set]) are
handling the nested-json-objects case in a fairly brain-dead fashion to
start with. I would
On 06/20/2014 11:26 AM, Joey Caughey wrote:
I’m having an issue with JSON requests in Postgres and was wondering
if anyone had an answer.
I have an orders table with a field called “json_data”.
In the json data there is a plan’s array with an id value in them.
{ plan”: { “id”: “1” } } }
I
On 06/19/2014 06:33 PM, Josh Berkus wrote:
Tom,
ISTM our realistic options are for seconds or msec as the unit. If it's
msec, we'd be limited to INT_MAX msec or around 600 hours at the top end,
which seems like enough to me but maybe somebody thinks differently?
Seconds are probably OK but
On 06/18/2014 09:34 AM, Tom Lane wrote:
Craig Ringer cr...@2ndquadrant.com writes:
I posted about a possible packaging issue with RHEL 6 PGDG packages for
9.4beta on pgsql-yum-pkg, but things are pretty quiet over there (a
prior mail asking about what happened with moving to git hasn't had a
I have released version 4.13 of the PostgreSQL Buildfarm client.
This can be downloaded from
http://www.pgbuildfarm.org/downloads/releases/build-farm-4_13.tgz
Changes in this release (from the git log):
fcc182b Don't run TestCollateLinuxUTF8 on unsupported branches.
273af50 Don't run
On 06/02/2014 11:38 AM, Andrew Dunstan wrote:
On 06/02/2014 10:22 AM, Andrew Dunstan wrote:
On 06/02/2014 10:02 AM, Robert Haas wrote:
On Thu, May 29, 2014 at 7:34 AM, Dmitry Dolgov
9erthali...@gmail.com wrote:
I'm little confused by the convertJsonbValue functon at jsonb_utils.c
Maybe I
I went to have a look at documenting the jsonb comparison operators, and
found that the docs on comparison operators contain this:
Comparison operators are available for all relevant data types.
They neglect to specify further, however. This doesn't seem very
satisfactory. How is a user
On 06/17/2014 07:25 PM, Andres Freund wrote:
On 2014-06-17 19:22:07 -0400, Tom Lane wrote:
Andrew Dunstan and...@dunslane.net writes:
I went to have a look at documenting the jsonb comparison operators, and
found that the docs on comparison operators contain this:
Comparison operators
On 06/15/2014 04:58 PM, Josh Berkus wrote:
I've been poking at the various json-query syntaxes you forwarded, and
none of them really work for the actual jsquery features. Also, the
existing syntax has the advantage of being *simple*, relatively
speaking, and reasonably similar to JSONPATH.
On 06/05/2014 08:08 PM, David E. Wheeler wrote:
Oleg, Teodor, and Hackers:
Love what you’re doing with JSQuery. I’m curious, though, whether you
considered adopting an existing syntax, such as JSONPath.
http://goessner.net/articles/JsonPath/
Might be easier for people to pick up and use.
On 06/04/2014 10:03 AM, Tom Lane wrote:
I just chanced to notice that if someone were to change the value for
LOBLKSIZE and recompile, there'd be nothing to stop him from starting
that postmaster against an existing database, even though it would
completely misinterpret and mangle any data in
On 06/04/2014 10:27 AM, Andres Freund wrote:
On 2014-06-04 10:25:07 -0400, Andrew Dunstan wrote:
If we did an initdb-requiring change for 9.4 could we piggy-back this onto
it?
Do you know of a problem requiring that?
No, just thinking ahead.
cheers
andrew
--
Sent via pgsql-hackers
On 06/04/2014 03:50 PM, Robert Haas wrote:
On Wed, Jun 4, 2014 at 2:52 PM, Tom Lane t...@sss.pgh.pa.us wrote:
I just noticed that we had not one, but two commits in 9.4 that added
fields to pg_control. And neither one changed PG_CONTROL_VERSION.
This is inexcusable sloppiness on the part of
On 06/03/2014 04:45 PM, Tom Lane wrote:
Peter Eisentraut pete...@gmx.net writes:
This was solved back in the day for the xml type, which has essentially
the same requirement, by adding an ISO-8601-compatible output option to
EncodeDateTime(). See map_sql_value_to_xml_value() in xml.c. You
On 06/03/2014 05:53 PM, Tom Lane wrote:
Josh Berkus j...@agliodbs.com writes:
Out of curiosity, how much harder would it have been just to abort the
transaction? I think breaking the connection is probably the right
behavior, but before folks start arguing it out, I wanted to know if
aborting
On 06/02/2014 10:02 AM, Robert Haas wrote:
On Thu, May 29, 2014 at 7:34 AM, Dmitry Dolgov 9erthali...@gmail.com wrote:
I'm little confused by the convertJsonbValue functon at jsonb_utils.c
Maybe I misunderstood something, so I need help =)
if (IsAJsonbScalar(val) || val-type == jbvBinary)
On 06/02/2014 10:22 AM, Andrew Dunstan wrote:
On 06/02/2014 10:02 AM, Robert Haas wrote:
On Thu, May 29, 2014 at 7:34 AM, Dmitry Dolgov
9erthali...@gmail.com wrote:
I'm little confused by the convertJsonbValue functon at jsonb_utils.c
Maybe I misunderstood something, so I need help
On 06/01/2014 05:35 PM, Tom Lane wrote:
I wrote:
3. Try to select some more portable non-ASCII character, perhaps U+00A0
(non breaking space) or U+00E1 (a-acute). I think this would probably
work for most encodings but it might still fail in the Far East. Another
objection is that the
On 05/30/2014 01:41 PM, Tom Lane wrote:
Andrew Dunstan and...@dunslane.net writes:
If we're going to construct varlena objects inside a StringInfo, maybe
we need a proper API for it. Isn't there a danger that data member of
the StringInfo won't be properly aligned to allow us to do
On 05/30/2014 09:35 AM, Teodor Sigaev wrote:
Hi!
jsonb operators -text, -text,-int, -int use inefficient methods
to access to needed field, proportional O(N/2). Attached patch
suggests for text operators O(log(N)) and for integer - O(1). The
fuctions with fast access already are existed in
On 05/30/2014 11:08 AM, Andrew Dunstan wrote:
On 05/30/2014 09:35 AM, Teodor Sigaev wrote:
Hi!
jsonb operators -text, -text,-int, -int use inefficient methods
to access to needed field, proportional O(N/2). Attached patch
suggests for text operators O(log(N)) and for integer - O(1
On 05/30/2014 01:30 PM, Oleg Bartunov wrote:
The patch really improves access performance to jsonb. On the
delicious bookmarks I got 5 times better performance.Now jsonb
outperforms json on simple access (slide 12 of pgcon presentation) by
103 times !
(Oleg, please try not to top-post)
On 05/29/2014 07:55 AM, Teodor Sigaev wrote:
# select '\uaBcD'::json;
json
--
\uaBcD
but
# select '\uaBcD'::jsonb;
ERROR: invalid input syntax for type json
LINE 1: select '\uaBcD'::jsonb;
^
DETAIL: Unicode escape values cannot be used for code point values
On 05/29/2014 08:00 AM, Teodor Sigaev wrote:
postgres=# select '[\u]'::json-0;
?column?
--
\u
(1 row)
Time: 1,294 ms
postgres=# select '[\u]'::jsonb-0;
?column?
---
\\u
(1 row)
It seems to me that escape_json() is wrongly used in
On 05/29/2014 08:21 AM, Andres Freund wrote:
On 2014-05-29 08:14:48 -0400, Peter Eisentraut wrote:
On 5/27/14, 10:37 PM, Tom Lane wrote:
If you don't like this change, we can revert it and also revert the upgrade to
2.69.
Nobody else appears to be concerned, but I would have preferred this
On 05/29/2014 08:15 AM, Andrew Dunstan wrote:
On 05/29/2014 08:00 AM, Teodor Sigaev wrote:
postgres=# select '[\u]'::json-0;
?column?
--
\u
(1 row)
Time: 1,294 ms
postgres=# select '[\u]'::jsonb-0;
?column?
---
\\u
(1 row)
It seems to me that escape_json
On 05/29/2014 02:38 PM, Tom Lane wrote:
Josh Kupershmidt schmi...@gmail.com writes:
On Wed, May 28, 2014 at 11:23 PM, Tom Lane t...@sss.pgh.pa.us wrote:
I've just committed regression test adjustments to prevent that from
being a failure case, but I am confused about why it's happening.
I
On 05/29/2014 05:41 PM, Josh Kupershmidt wrote:
On Thu, May 29, 2014 at 4:06 PM, Andrew Dunstan and...@dunslane.net wrote:
Almost all my critters run in VMs (all but jacana and bowerbird).
They're not running on OpenVZ, are they? `ifconfig` on shearwater says:
[...]
and it seems this all
Here is a draft patch for some of the issues to do with unicode escapes
that Teodor raised the other day.
I think it does the right thing, although I want to add a few more
regression cases before committing it.
Comments welcome.
cheers
andrew
diff --git a/src/backend/utils/adt/json.c
On 05/27/2014 11:55 PM, Robert Haas wrote:
On Tue, May 27, 2014 at 5:00 PM, Tom Lane t...@sss.pgh.pa.us wrote:
I'd be inclined to think a more useful answer to this issue would be to
make json.c special-case timestamps, as it already does for numerics.
I wonder if anyone besides me is nervous
On 05/27/2014 07:25 PM, Andrew Dunstan wrote:
On 05/27/2014 07:17 PM, Tom Lane wrote:
Stephen Frost sfr...@snowman.net writes:
* Andrew Dunstan (and...@dunslane.net) wrote:
Given that this would be a hard coded behaviour change, is it too
late to do this for 9.4?
No, for my 2c.
If we do
I've been on the receiving end of a couple of mumbles about the fact
that the JSON rendering code ignores casts of builtin types to JSON.
This was originally done as an optimization to avoid doing cache lookups
for casts for things we knew quite well how to turn into JSON values
(unlike, say,
On 05/27/2014 03:57 PM, Heikki Linnakangas wrote:
On 05/27/2014 10:53 PM, Andrew Dunstan wrote:
I've been on the receiving end of a couple of mumbles about the fact
that the JSON rendering code ignores casts of builtin types to JSON.
This was originally done as an optimization to avoid doing
On 05/27/2014 05:43 PM, Hannu Krosing wrote:
On 05/27/2014 11:00 PM, Tom Lane wrote:
See src/backend/utils/adt/json.c:json_categorize_type() lines 1280-1300.
When rendering some value as part of a json string, if a cast exists
from the data type to json, then the cast function is used to
On 05/27/2014 07:17 PM, Tom Lane wrote:
Stephen Frost sfr...@snowman.net writes:
* Andrew Dunstan (and...@dunslane.net) wrote:
Given that this would be a hard coded behaviour change, is it too
late to do this for 9.4?
No, for my 2c.
If we do it by adding casts then it'd require an initdb
On 05/20/2014 09:42 AM, Tom Lane wrote:
Regarding clock skew, I think we can do better then what you suggest.
The web transaction code in the client adds its own timestamp just
before running the web transaction. It would be quite reasonable to
reject reports from machines with skewed clocks
On 05/20/2014 03:39 AM, Rohit Goyal wrote:
Hi All,
Just adding the actual error again.
I run the the *dbt2-pgsql-build-db -w 1 *
Output directory of data files: current directory
*Generating data files for 1 warehouse(s)...*
*Generating item table data...*
*BEGIN*
*ERROR: invalid byte
On 05/20/2014 07:09 AM, Tom Lane wrote:
Robert Haas robertmh...@gmail.com writes:
On Mon, May 19, 2014 at 7:58 PM, Andrew Dunstan and...@dunslane.net wrote:
Well, the original code was put in for a reason, presumably that we were
getting some stale data and wanted to exclude it. So I'm
On 05/20/2014 03:59 PM, Gavin Flower wrote:
On 21/05/14 01:42, Tom Lane wrote:
Andrew Dunstanand...@dunslane.net writes:
On 05/20/2014 07:09 AM, Tom Lane wrote:
Robert's got a point here. In my usage, the annoying thing is not animals
that take a long time to report in; it's the ones that
I have just noticed as I am preparing my slides well ahead of time :-)
that we haven't documented the inequality operators of jsonb. Is that
deliberate or an oversight?
cheers
andrew
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your
On 05/19/2014 03:40 PM, Tomas Vondra wrote:
On 17.5.2014 22:35, Tomas Vondra wrote:
On 17.5.2014 19:58, Andrew Dunstan wrote:
On 05/15/2014 07:47 PM, Tomas Vondra wrote:
On 15.5.2014 22:07, Andrew Dunstan wrote:
Yes, I've seen that. Frankly, a test that takes something like 500
hours
On 05/19/2014 05:37 PM, Tomas Vondra wrote:
IMHO the problem is that d6a97674 was the last revision in the
REL9_3_STABLE branch when the test started (00:14), but at 06:06
777d07d7 got committed. So the check at the end failed, because the
tested revision was suddenly ~2 days over the limit.
On 05/05/2014 07:26 PM, Andrew Dunstan wrote:
On 05/05/2014 07:16 PM, Bruce Momjian wrote:
Current text is:
Add structured (non-text) data type (JSONB) for storing JSON data
(Oleg
Bartunov, Teodor Sigaev, Alexander Korotkov, Peter Geoghegan, and
Andrew
Dunstan
On 05/15/2014 07:47 PM, Tomas Vondra wrote:
On 15.5.2014 22:07, Andrew Dunstan wrote:
Yes, I've seen that. Frankly, a test that takes something like 500
hours is a bit crazy.
Maybe. It certainly is not a test people will use during development.
But if it can detect some hard-to-find errors
On 05/16/2014 12:43 PM, Heikki Linnakangas wrote:
On 05/16/2014 06:05 PM, Tom Lane wrote:
Quite some time ago, we made the chr() function accept Unicode code
points
up to U+1F, which is the largest value that will fit in a 4-byte
UTF8
string. It was pointed out to me though that RFC3629
On 05/15/2014 12:43 PM, Tomas Vondra wrote:
Hi all,
today I got a few of errors like these (this one is from last week, though):
Status Line: 493 snapshot too old: Wed May 7 04:36:57 2014 GMT
Content:
snapshot to old: Wed May 7 04:36:57 2014 GMT
on the new buildfarm animals. I
On 05/15/2014 03:57 PM, Tomas Vondra wrote:
How long does a CLOBBER_CACHE_RECURSIVELY run take? days or weeks seems
kinda nuts.
I don't know. According to this comment from cache/inval.c, it's expected
to be way slower (~100x) compared to CLOBBER_CACHE_ALWAYS.
/*
* Test code to force cache
On 05/15/2014 04:30 PM, Stefan Kaltenbrunner wrote:
On 05/15/2014 07:46 PM, Andrew Dunstan wrote:
On 05/15/2014 12:43 PM, Tomas Vondra wrote:
Hi all,
today I got a few of errors like these (this one is from last week,
though):
Status Line: 493 snapshot too old: Wed May 7 04:36:57 2014
On 05/15/2014 06:37 PM, Rohit Goyal wrote:
Hi All,
I am using centOS6 and after all confugration, I run the below command
*dbt2-run-workload -a pgsql -d 120 -w 1 -o /tmp/result -c 10
*
*Error:*
Stage 3. Processing of results...
Killing client...
waiting for server to shut down done
On 05/14/2014 08:15 AM, Heikki Linnakangas wrote:
On 05/09/2014 02:56 AM, Noah Misch wrote:
On Thu, May 08, 2014 at 12:14:44PM -0400, Tom Lane wrote:
Andrew Dunstan and...@dunslane.net writes:
I'm pretty sure we need this on Mingw - this SYSTEMQUOTE stuff dates
back well before 8.3, IIRC
On 05/14/2014 11:02 AM, Tom Lane wrote:
I wrote:
As far as Windows goes, we could certainly use #ifdef WIN32 to print
some different text, if anyone can write down what it should be.
Some googling suggests that on Windows, setlocale pays no attention
to environment variables but gets a value
On 05/13/2014 02:39 PM, Tomas Vondra wrote:
On 13.5.2014 20:27, Tomas Vondra wrote:
Hi all,
a few days ago I switched magpie into an LXC container, and while
fixinig unrelated issue there, I noticed that although the tests seemed
to run, some of the results are actually rubbish because of
On 05/13/2014 03:40 PM, Tom Lane wrote:
Tomas Vondra t...@fuzzy.cz writes:
On 13.5.2014 21:03, Andrew Dunstan wrote:
On 05/13/2014 02:39 PM, Tomas Vondra wrote:
However in the lastrun-logs I see 81 files, and upon closer inspection
it seems that pretty much logs for all custom locales (cs_CZ
On 05/13/2014 04:14 PM, Tom Lane wrote:
Heikki Linnakangas hlinnakan...@vmware.com writes:
On 05/13/2014 09:58 PM, Tom Lane wrote:
... If so the issue is presumably
that the environment variable(s) were set to incorrect values. While
we *could* abort in that situation, I've never heard of
On 05/12/2014 07:10 AM, Pavel Stehule wrote:
Hello
I am trying to compile PL/v8 without success. I have Postgres
installed via compilation from source code.
After make I got errors
[pavel@localhost plv8-1.4.2]$ make
g++ -Wall -O2 -I. -I./ -I/usr/local/pgsql/include/server
On 05/10/2014 04:42 PM, Heikki Linnakangas wrote:
The main difference between the two opclasses from a user's standpoint
is not whether they hash or not. The big difference is that one
indexes complete paths from the root, and the other indexes just the
leaf level. For example, if you have
On 05/09/2014 10:07 AM, Tom Lane wrote:
After further reflection I think we should lose the TYPCATEGORY_NUMERIC
business too. ruleutils.c hard-wires the set of types it will consider
to be numeric, and I see no very good reason not to do likewise here.
That will remove the need to look up the
On 05/09/2014 11:25 AM, Robert Haas wrote:
On Fri, May 9, 2014 at 11:18 AM, Alvaro Herrera
alvhe...@2ndquadrant.com wrote:
I guess it depends how likely we think that a different compiler will
change the behavior of the shared invalidation queue. Somebody else
would have to answer that. If
On 05/08/2014 11:19 AM, Tom Lane wrote:
Heikki Linnakangas hlinnakan...@vmware.com writes:
On 05/08/2014 08:01 AM, Michael Paquier wrote:
Since commit a692ee5, code compilation on windows is full of warnings
caused by the re-definitions of popen and pclose:
Hmm. Does the MinGW version of
On 05/08/2014 11:30 AM, Tom Lane wrote:
Michael Paquier michael.paqu...@gmail.com writes:
Since commit 60ff2fd introducing the centralizated getopt-related
things in a global header file, build on Windows with mingw is failing
Hm, buildfarm member narwhal doesn't seem to be having any such
On 05/08/2014 12:14 PM, Tom Lane wrote:
Andrew Dunstan and...@dunslane.net writes:
I'm pretty sure we need this on Mingw - this SYSTEMQUOTE stuff dates
back well before 8.3, IIRC, which is when we first got full MSVC support.
I tried googling for some info on this, and got a number of hits
On 05/08/2014 12:21 PM, Tomas Vondra wrote:
On 6.5.2014 23:01, Tomas Vondra wrote:
On 6.5.2014 22:24, Tom Lane wrote:
Tomas Vondra t...@fuzzy.cz writes:
I recall there was a call for more animals with CLOBBER_CACHE_ALWAYS
some time ago, so I went and enabled that on all three animals.
On 05/08/2014 04:09 PM, Alvaro Herrera wrote:
Andrew Dunstan wrote:
Here is what I do on my FreeBSD VM. I have 2 animals, nightjar and
friarbird. They have the same buildroot. friarbird is set up to
build with CLOBBER_CACHE_ALWAYS, building just HEAD and just testing
C locale; nightjar builds
On 05/08/2014 04:54 PM, Andrew Dunstan wrote:
Why? This was actually discussed when I set this up and Tom opined
that a once a day run with CLOBBER_CACHE_ALWAYS was plenty. It takes
about 4 /12 hours. The rest of the time nightjar runs. friarbird runs
a bit after midnight US East Coast
On 05/08/2014 05:21 PM, Alvaro Herrera wrote:
Andrew Dunstan wrote:
I really don't get what your objection to the setup is. And no, I
don't want them to run concurrently, I'd rather spread out the
cycles.
I wasn't objecting, merely an observation. Note that Tomas mentioned
he's okay
On 05/07/2014 10:12 AM, Andres Freund wrote:
On 2014-05-07 10:07:07 -0400, Tom Lane wrote:
In the meantime, it seems like there is an emerging consensus that nobody
much likes the existing auto-tuning behavior for effective_cache_size,
and that we should revert that in favor of just increasing
On 05/07/2014 02:52 PM, Andres Freund wrote:
On 2014-05-07 14:48:51 -0400, Tom Lane wrote:
Andres Freund and...@anarazel.de writes:
* The jentry representation should be changed so it's possible to get the type
of a entry without checking individual types. That'll make code like
On 05/07/2014 04:13 PM, Tom Lane wrote:
A README file would be better,
perhaps, but there's not a specific directory associated with the jsonb
code; so I think this sort of info belongs either in jsonb.h or in the
file header comment for jsonb_gin.c.
Is there any reason we couldn't have a
On 05/06/2014 05:54 PM, Robert Haas wrote:
On Tue, May 6, 2014 at 4:38 PM, Simon Riggs si...@2ndquadrant.com wrote:
I read the code, think what to say and then say what I think, not
rely on dogma.
I tried to help years ago by changing the docs on e_c_s, but that's
been mostly ignored down
On 05/05/2014 09:38 AM, Bruce Momjian wrote:
On Sun, May 4, 2014 at 10:24:54AM -0400, Andrew Dunstan wrote:
On 05/04/2014 10:12 AM, Petr Jelinek wrote:
On 04/05/14 14:46, Bruce Momjian wrote:
I have completed the initial version of the 9.4 release notes. You can
view them here:
http
On 05/05/2014 11:20 AM, Pavel Stehule wrote:
How about:
UPDATE foo SET (foo).* = (1,2,3);
It is looking little bit strange
I like previous proposal UPDATE foo SET foo = (1,2,3);
What if the table has a field called foo? Won't it then be ambiguous?
cheers
andrew
--
Sent via
On 05/05/2014 02:33 PM, Josh Berkus wrote:
On 05/05/2014 11:31 AM, Bruce Momjian wrote:
JSONB values are also mapped to SQL scalar data types, rather
than being treated always as strings.
+ ... allowing for correct sorting of JSON according to internal datums.
The problem is that
On 05/05/2014 07:16 PM, Bruce Momjian wrote:
On Mon, May 5, 2014 at 10:58:57AM -0700, Peter Geoghegan wrote:
On Mon, May 5, 2014 at 8:28 AM, Andrew Dunstan and...@dunslane.net wrote:
How about:
This data type allows for faster access to values in the json document
and faster and more
On 05/05/2014 07:34 PM, Peter Geoghegan wrote:
On Mon, May 5, 2014 at 4:26 PM, Andrew Dunstan and...@dunslane.net wrote:
After all, everything that's not a number or boolean is typed as text (just
as it is in JSON). We don't, for example, map anything to timestamp types.
JSON doesn't have
) for storing JSON
data (Oleg Bartunov, Teodor Sigaev, Peter Geoghegan and Andrew Dunstan)
+/para
+
+para
+ This data type allows faster indexing and access to json
keys/value pairs.
+/para
+ /listitem
I think the explanation should be expanded to say
On 05/03/2014 09:17 AM, Marko Tiikkaja wrote:
Hi all,
Now that we're on the topic of view deparsing, what are your thoughts
on making this less painful?
local:marko=#* create view foov as select exists(select * from foo);
CREATE VIEW
local:marko=#* \d+ foov
View
On 05/03/2014 09:55 AM, Peter Krauss wrote:
My notion of anonymous record, and the need of this kind of
higher-order type, are discussed in the links below,
http://stackoverflow.com/q/23439240
Functions can not to /return individual items of a record/
http://stackoverflow.com/q/21246201
On 05/03/2014 12:42 PM, Tomas Vondra wrote:
On 3.5.2014 03:07, Noah Misch wrote:
More coverage of non-gcc compilers would be an asset to the buildfarm.
Does that include non-gcc compilers on Linux/x86 platforms?
Magpie is pretty much dedicated to the buildfarm, and it's pretty much
doing
On 04/30/2014 02:35 AM, Heikki Linnakangas wrote:
On 04/30/2014 01:27 AM, Stephen Frost wrote:
* Tom Lane (t...@sss.pgh.pa.us) wrote:
Josh Berkus j...@agliodbs.com writes:
... so let's stop using that phrase, OK?
http://meyerweb.com/eric/comment/chech.html
Shrug ... what I see there is a
On 04/30/2014 06:31 AM, Heikki Linnakangas wrote:
Andrew: you have a cygwin installation, don't you? Could you test if
pg_ctl start works when the binaries are installed to a path that
contains both a space and an @ sign, like C:\white
space\at@sign\install. I suspect it doesn't, but the
On 04/30/2014 11:58 AM, Andrew Dunstan wrote:
On 04/30/2014 06:31 AM, Heikki Linnakangas wrote:
Andrew: you have a cygwin installation, don't you? Could you test if
pg_ctl start works when the binaries are installed to a path that
contains both a space and an @ sign, like C:\white
space
On 04/30/2014 03:03 PM, Andrew Dunstan wrote:
On 04/30/2014 11:58 AM, Andrew Dunstan wrote:
On 04/30/2014 06:31 AM, Heikki Linnakangas wrote:
Andrew: you have a cygwin installation, don't you? Could you test if
pg_ctl start works when the binaries are installed to a path that
contains
On 04/29/2014 02:56 AM, Heikki Linnakangas wrote:
On 04/28/2014 10:32 PM, Tom Lane wrote:
Robert Haas robertmh...@gmail.com writes:
I have to admit it's been a few years since I've had to play with
WAL_DEBUG, so I don't really remember what I was trying to do. But I
don't see any real
On 04/22/2014 08:15 AM, MauMau wrote:
Are you planning to include the above features in 9.5 and 9.6? Are you
recommending other developers not implement these features to avoid
duplication of work with AXLE?
Without pointing any fingers, I should note that I have learned the hard
way
On 04/22/2014 08:04 AM, Simon Riggs wrote:
On 22 April 2014 00:24, Josh Berkus j...@agliodbs.com wrote:
On 04/21/2014 03:41 PM, Simon Riggs wrote:
Storage Efficiency
* Compression
* Column Orientation
You might look at turning this:
http://citusdata.github.io/cstore_fdw/
... into a more
On 04/22/2014 01:36 AM, Joshua D. Drake wrote:
On 04/21/2014 06:19 PM, Andrew Dunstan wrote:
If we never start we'll never get there.
I can think of several organizations that might be approached to donate
hardware.
Like .Org?
We have a hardware farm, a rack full of hardware
1001 - 1100 of 8267 matches
Mail list logo
