Hi Palle,
thanks for the extremely quick response!
In that case I will include the patch in Postgres.app. Missing support for
per-column collations is preferable to missing support for the standard locale!
I'll have a look at the per-column collation support, it would be great if
PostgreSQL
So, Here are reworked patches for the whole set, with the following changes:
- Found why replay was failing, xlogreader.c took into account BLCKSZ
- hole while it should have taken into account the compressed data
length when fetching a compressed block image.
- Reworked pglz portion to have it
On Wed, Nov 26, 2014 at 8:41 AM, Palle Girgensohn gir...@pingpong.net wrote:
Hi!
This is indeed a very well tested patch as we've run it in production for 8+
years on 20+ systems.
It is not included upstreams mainly because I did ask for it to happen. I've
been aiming to do it but haven't
26 nov 2014 kl. 09:58 skrev Magnus Hagander mag...@hagander.net:
On Wed, Nov 26, 2014 at 8:41 AM, Palle Girgensohn gir...@pingpong.net wrote:
Hi!
This is indeed a very well tested patch as we've run it in production for 8+
years on 20+ systems.
It is not included upstreams mainly
Re: Heikki Linnakangas 2014-11-25 5474b848.3060...@vmware.com
db1 is registered in pg_database, but the directory is missing on
disk.
Yeah, DROP DATABASE cheats. It deletes all the files first, and commits the
transaction only after that. There's this comment at the end of dropdb()
On 11/26/2014 11:19 AM, Christoph Berg wrote:
Re: Heikki Linnakangas 2014-11-25 5474b848.3060...@vmware.com
db1 is registered in pg_database, but the directory is missing on
disk.
Yeah, DROP DATABASE cheats. It deletes all the files first, and commits the
transaction only after that. There's
One of the
big arguments against bringing it in then (because it worked) was that
we'd bring in another compile time dependency that's actually larger
than PostgreSQL itself.
Magnus: I don't see how this is a problem as long as using ICU is *optional*.
On systems with a working strcoll there
26 nov 2014 kl. 10:36 skrev Jakob Egger ja...@eggerapps.at:
One of the
big arguments against bringing it in then (because it worked) was that
we'd bring in another compile time dependency that's actually larger
than PostgreSQL itself.
Magnus: I don't see how this is a problem as long as
Bear in mind that this might alter the way indexes are built. From the top of
my head, I just can't remember if this is true or not. I'm probably wrong?
Magnus? You would have to try.
That's why I want to include it in the first version of 9.4, when people need
to dump reload their
26 nov 2014 kl. 10:48 skrev Jakob Egger ja...@eggerapps.at:
Bear in mind that this might alter the way indexes are built. From the top
of my head, I just can't remember if this is true or not. I'm probably
wrong? Magnus? You would have to try.
That's why I want to include it in the
On Wed, Nov 26, 2014 at 9:48 AM, Jakob Egger ja...@eggerapps.at wrote:
Bear in mind that this might alter the way indexes are built. From the top
of my head, I just can't remember if this is true or not. I'm probably
wrong? Magnus? You would have to try.
That's why I want to include it in
Am 26.11.2014 um 11:05 schrieb Dave Page dp...@postgresql.org:
You may want to bear in mind that postgres.app is on the main PG
downloads page on the website. If you're patching Postgres to add a
feature like this, it would become a fork and would have to be moved
out of the PostgreSQL Core
Hi all,
We are facing following issue in postgresql 9.1.3 in using arrow key in Solaris
platform.
Can you please help us to resolve it or any new release has fix for this or any
workaround for this?
issue: psql client generates a core when up arrow is used twice.
Platfrom: Solaris
On Wed, Nov 26, 2014 at 10:13 AM, Jakob Egger ja...@eggerapps.at wrote:
Am 26.11.2014 um 11:05 schrieb Dave Page dp...@postgresql.org:
You may want to bear in mind that postgres.app is on the main PG
downloads page on the website. If you're patching Postgres to add a
feature like this, it
On Wed, Nov 26, 2014 at 11:13 AM, Jakob Egger ja...@eggerapps.at wrote:
Am 26.11.2014 um 11:05 schrieb Dave Page dp...@postgresql.org:
You may want to bear in mind that postgres.app is on the main PG
downloads page on the website. If you're patching Postgres to add a
feature like this, it
Am 26.11.2014 um 11:20 schrieb Dave Page dp...@postgresql.org:
On Wed, Nov 26, 2014 at 10:13 AM, Jakob Egger ja...@eggerapps.at wrote:
Am 26.11.2014 um 11:05 schrieb Dave Page dp...@postgresql.org:
You may want to bear in mind that postgres.app is on the main PG
downloads page on the
Is it broken *worse* in 9.4 than it was in previous versions?
No.
Because the indices need to be rebuilt, the only realistic opportunity for
applying this patch to Postgres.app is when releasing a major new version,
since then people need to migrate their data anyway. That's why I wanted to
Hello,
I would like to contribute few points.
XLogInsertRecord(XLogRecData *rdata, XLogRecPtr fpw_lsn)
RedoRecPtr = Insert-RedoRecPtr;
}
doPageWrites = (Insert-fullPageWrites || Insert-forcePageWrites);
doPageCompression = (Insert-fullPageWrites ==
I had to make oracle_fdw work with PostgreSQL compiled using
--with-ldap. The issue there is that Oracle's client library has the
delightful property of linking against a ldap library they bundle that
has symbol conflicts with OpenLDAP. At PostgreSQL startup libldap is
loaded, so when libclntsh.so
Re: Heikki Linnakangas 2014-11-26 54759bc0.4070...@vmware.com
Oh ok. So this is an artifact of the non-transactionality (is this a
word?) of CREATE DATABASE.
DROP DATABASE. CREATE DATABASE is a different story. It does similar
non-transactional tricks and has similar issues, but it's a
2014-11-26 9:58 GMT+01:00 Magnus Hagander mag...@hagander.net:
On Wed, Nov 26, 2014 at 8:41 AM, Palle Girgensohn gir...@pingpong.net
wrote:
Hi!
This is indeed a very well tested patch as we've run it in production
for 8+
years on 20+ systems.
It is not included upstreams mainly
On 11/26/14 8:55 AM, Pavel Stehule wrote:
* should be assertions globally enabled/disabled? - I have no personal
preference in this question.
I think so. The way I would use this function is to put expensive
checks into strategic locations which would only run when developing
locally (and
Ants Aasma wrote:
I had to make oracle_fdw work with PostgreSQL compiled using
--with-ldap. The issue there is that Oracle's client library has the
delightful property of linking against a ldap library they bundle that
has symbol conflicts with OpenLDAP. At PostgreSQL startup libldap is
Adam,
* Adam Brightwell (adam.brightw...@crunchydatasolutions.com) wrote:
I am simply breaking this out into its own thread from the discussion on
additional role attributes (
http://www.postgresql.org/message-id/20141015052259.gg28...@tamriel.snowman.net
).
Makes sense to me, thanks.
Tom,
First of all, thanks for your help on IRC last time with that CREATE
INDEX memory consumption problem.
As has been pointed out in a stackexchange answer to my question[1], it
is indeed the limitation of pre-9.4 versions, but the limit is imposed
on memtuples array, rather than total memory
On Sun, Nov 23, 2014 at 3:38 PM, Andres Freund and...@2ndquadrant.com wrote:
I'm not really particular about which way we go with the specific
wording (suggestions welcome..) but the inconsistency should be dealt
with.
Meh.
+1 for meh. I don't mind making things consistent if it can be done
Jeff Janes wrote:
This is what I get in the log from the attempted restart:
PST LOG: database system was interrupted; last known up at 2014-11-25
15:40:33 PST
PST LOG: database system was not properly shut down; automatic recovery in
progress
PST LOG: redo starts at 84/EF80
PST
26 nov 2014 kl. 11:44 skrev Jakob Egger ja...@eggerapps.at:
Am 26.11.2014 um 11:20 schrieb Dave Page dp...@postgresql.org:
On Wed, Nov 26, 2014 at 10:13 AM, Jakob Egger ja...@eggerapps.at wrote:
Am 26.11.2014 um 11:05 schrieb Dave Page dp...@postgresql.org:
You may want to bear in
* Robert Haas (robertmh...@gmail.com) wrote:
On Sun, Nov 23, 2014 at 3:38 PM, Andres Freund and...@2ndquadrant.com wrote:
I'm not really particular about which way we go with the specific
wording (suggestions welcome..) but the inconsistency should be dealt
with.
Meh.
+1 for meh. I
Alex,
* Alex Shulgin (a...@commandprompt.com) wrote:
Tom,
First of all, thanks for your help on IRC last time with that CREATE
INDEX memory consumption problem.
Doubt it was Tom, but if it was, wanna share what channel on IRC it was?
:D
Now my question, is it feasible to back-patch this
On 2014-11-26 08:33:10 -0500, Stephen Frost wrote:
* Robert Haas (robertmh...@gmail.com) wrote:
On Sun, Nov 23, 2014 at 3:38 PM, Andres Freund and...@2ndquadrant.com
wrote:
I'm not really particular about which way we go with the specific
wording (suggestions welcome..) but the
I find it hard to believe the original premise of this thread. We knew
there were some problems with OSX and FreeBSD but surely they can't be
completely broken? What happens if you run ls with your locale set
to something like fr_FR.UTF8 ? Does Apple not sell Macs in countries
other than the US?
Here's a patch. This creates a new subdir src/test/modules and places
the five initially proposed modules in there. They continue to have
their makefile with the same ifdef USE_PGXS pattern; they are no longer
installed by default.
Because many of them had either test in their names or some
On Wed, Nov 26, 2014 at 9:27 AM, Alvaro Herrera
alvhe...@2ndquadrant.com wrote:
Here's a patch. This creates a new subdir src/test/modules and places
the five initially proposed modules in there. They continue to have
their makefile with the same ifdef USE_PGXS pattern; they are no longer
On Wed, Nov 26, 2014 at 12:27 PM, Alvaro Herrera alvhe...@2ndquadrant.com
wrote:
Here's a patch. This creates a new subdir src/test/modules and places
the five initially proposed modules in there. They continue to have
their makefile with the same ifdef USE_PGXS pattern; they are no longer
This is pretty bulky, but really the vast majority of the changes here
are just git mv.
--
Álvaro Herrerahttp://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training Services
test_modules.patch.gz
Description: application/gzip
--
Sent via pgsql-hackers mailing
On 11/26/2014 02:16 AM, M Tarkeshwar Rao wrote:
Hi all,
We are facing following issue in postgresql 9.1.3 in using arrow key in
Solaris platform.
*Can you please help us to resolve it or any new release has fix for
this or any workaround for this?*
Would seem to me to be an interaction
* Andres Freund (and...@2ndquadrant.com) wrote:
On 2014-11-26 08:33:10 -0500, Stephen Frost wrote:
Doesn't that argument then apply to the other messages which I pointed
out in my follow-up to Andres, where the detailed info is in the hint
and the main error message is essentially
Stephen Frost sfr...@snowman.net writes:
* Alex Shulgin (a...@commandprompt.com) wrote:
Tom,
First of all, thanks for your help on IRC last time with that CREATE
INDEX memory consumption problem.
Doubt it was Tom, but if it was, wanna share what channel on IRC it was?
:D
Must've been my
Stephen Frost wrote:
* Andres Freund (and...@2ndquadrant.com) wrote:
On 2014-11-26 08:33:10 -0500, Stephen Frost wrote:
Doesn't that argument then apply to the other messages which I pointed
out in my follow-up to Andres, where the detailed info is in the hint
and the main error
On Nov 26, 2014, at 8:21 AM, Greg Stark st...@mit.edu wrote:
I find it hard to believe the original premise of this thread. We knew
there were some problems with OSX and FreeBSD but surely they can't be
completely broken?
Ever tried to use Spotlight for searching (English) on the Mac, not
Hello everyone,
For creating indexes on more than one column, it is useful to know the sort
order of each sort key. So now, if you run EXPLAIN in VERBOSE mode, you get
the sort order information in the order the sort keys are displayed - Lukas
- This patch is meant for discussion
- It’s
26 nov 2014 kl. 15:21 skrev Greg Stark st...@mit.edu:
I find it hard to believe the original premise of this thread. We knew
there were some problems with OSX and FreeBSD but surely they can't be
completely broken? What happens if you run ls with your locale set
to something like
* Tom Lane (t...@sss.pgh.pa.us) wrote:
In the context at hand, I think most of the messages in question are
currently phrased like must be superuser to do X. I'd be fine with
changing that to permission denied to do X, but not to just
permission denied.
Apologies for the terseness of my
On 2014-11-26 11:53:40 -0300, Alvaro Herrera wrote:
Stephen Frost wrote:
* Andres Freund (and...@2ndquadrant.com) wrote:
On 2014-11-26 08:33:10 -0500, Stephen Frost wrote:
Doesn't that argument then apply to the other messages which I pointed
out in my follow-up to Andres, where the
26 nov 2014 kl. 15:56 skrev Neil Tiffin ne...@neiltiffin.com:
On Nov 26, 2014, at 8:21 AM, Greg Stark st...@mit.edu wrote:
I find it hard to believe the original premise of this thread. We knew
there were some problems with OSX and FreeBSD but surely they can't be
completely broken?
On 2014-11-26 10:08:57 -0500, Tom Lane wrote:
Alvaro Herrera alvhe...@2ndquadrant.com writes:
This is pretty bulky, but really the vast majority of the changes here
are just git mv.
For ease of review, is there a way to get git to show just the diffs that
*aren't* git mv? (That is, show
26 nov 2014 kl. 14:06 skrev Palle Girgensohn gir...@pingpong.net:
Well, this discussion actually pushes the priority quite a bit for me --
someone else actually beeing interested about the patch... I thought it was
just me... :)=
By pushes the priority, I mean it gets more prioritized,
* Andres Freund (and...@2ndquadrant.com) wrote:
I don't see how you read the contrary from the guidelines:
The primary message should be short, factual, and avoid reference to
implementation details such as specific function names. Short means
should fit on one line under normal conditions.
Tom Lane wrote:
Alvaro Herrera alvhe...@2ndquadrant.com writes:
This is pretty bulky, but really the vast majority of the changes here
are just git mv.
For ease of review, is there a way to get git to show just the diffs that
*aren't* git mv? (That is, show changes in a file's content
On 2014-11-26 10:18:20 -0500, Stephen Frost wrote:
* Andres Freund (and...@2ndquadrant.com) wrote:
I don't see how you read the contrary from the guidelines:
The primary message should be short, factual, and avoid reference to
implementation details such as specific function names. Short
* Andres Freund (and...@2ndquadrant.com) wrote:
On 2014-11-26 10:18:20 -0500, Stephen Frost wrote:
* Andres Freund (and...@2ndquadrant.com) wrote:
I don't see how you read the contrary from the guidelines:
The primary message should be short, factual, and avoid reference to
Alex Shulgin a...@commandprompt.com writes:
Tom Lane t...@sss.pgh.pa.us writes:
Must've been my evil twin.
Sorry, I must be under false impression that RhodiumToad is *your* nick
on #postgresql at freenode. I don't recall who told me that, but I was
pretty sure it's you. :-p
That's Andrew
Alex == Alex Shulgin a...@commandprompt.com writes:
Tom Lane t...@sss.pgh.pa.us writes:
Must've been my evil twin.
Alex Sorry, I must be under false impression that RhodiumToad is
Alex *your* nick on #postgresql at freenode. I don't recall who
Alex told me that, but I was pretty sure
2014-11-26 13:31 GMT+01:00 Marko Tiikkaja ma...@joh.to:
On 11/26/14 8:55 AM, Pavel Stehule wrote:
* should be assertions globally enabled/disabled? - I have no personal
preference in this question.
I think so. The way I would use this function is to put expensive checks
into strategic
On Wed, Nov 26, 2014 at 3:48 PM, Michael Paquier
michael.paqu...@gmail.com wrote:
On Wed, Nov 19, 2014 at 1:37 AM, Simon Riggs si...@2ndquadrant.com wrote:
On 23 October 2014 00:21, Alvaro Herrera alvhe...@2ndquadrant.com wrote:
Attached patch is latest version patch I modified above.
Also, I
Andrew Gierth and...@tao11.riddles.org.uk writes:
Alex == Alex Shulgin a...@commandprompt.com writes:
Tom Lane t...@sss.pgh.pa.us writes:
Must've been my evil twin.
Alex Sorry, I must be under false impression that RhodiumToad is
Alex *your* nick on #postgresql at freenode. I don't
bo...@edookit.com writes:
The hstore_to_json_loose(hstore) produces an invalid JSON in the following
case:
SELECT hstore_to_json_loose(hstore(ARRAY ['name'], ARRAY ['1.'] :: TEXT
[]))
Output: {name: 1.}
The actual output is indeed incorrect as JSON does not permit `1.` - it must
be a
On 11/25/2014 11:46 PM, Michael Paquier wrote:
Hi all,
In the stuff I work on in a daily basis there are a couple of
extensions written in C++, compiling them with MSVC on Windows using
slightly-different scripts available in src/tools after copying them
directly in contrib/. However, the
Andrew Dunstan and...@dunslane.net writes:
This doesn't seem to me to be terribly well expressed (I know it's not your
fault, quite possibly it's mine.) Perhaps we should replace
[r]?[cyl](pp)?
with
(c|cpp|y|l|rc)
+1 ... the original coding is illegible already, not to mention wrong
On Wed, Nov 26, 2014 at 10:17 AM, Palle Girgensohn gir...@pingpong.net wrote:
26 nov 2014 kl. 14:06 skrev Palle Girgensohn gir...@pingpong.net:
Well, this discussion actually pushes the priority quite a bit for me --
someone else actually beeing interested about the patch... I thought
On 11/26/2014 11:19 AM, Tom Lane wrote:
bo...@edookit.com writes:
The hstore_to_json_loose(hstore) produces an invalid JSON in the following
case:
SELECT hstore_to_json_loose(hstore(ARRAY ['name'], ARRAY ['1.'] :: TEXT
[]))
Output: {name: 1.}
The actual output is indeed incorrect as JSON does
On 11/26/2014 11:48 AM, Andrew Dunstan wrote:
In json.c we now check numbers like this:
JsonLexContext dummy_lex;
boolnumeric_error;
...
dummy_lex.input = *outputstr == '-' ? outputstr + 1 : outputstr;
dummy_lex.input_length = strlen(dummy_lex.input);
On Wed, Nov 26, 2014 at 6:21 AM, Greg Stark st...@mit.edu wrote:
There were a number of problems with using ICU including the large
dependency and the limitations of the iterator model but the main
issue was that it's fundamentally a choice between being consistent
with every other application
On Wed, Nov 26, 2014 at 2:05 AM, Dave Page dp...@postgresql.org wrote:
You may want to bear in mind that postgres.app is on the main PG
downloads page on the website. If you're patching Postgres to add a
feature like this, it would become a fork and would have to be moved
out of the PostgreSQL
Robert Haas wrote:
On Wed, Nov 26, 2014 at 9:27 AM, Alvaro Herrera
alvhe...@2ndquadrant.com wrote:
Because many of them had either test in their names or some other
now-useless particle, I renamed them:
worker_spi - bgworker
test_decoding - logical_decoding
Alex Shulgin a...@commandprompt.com writes:
I can do that too, just need a hint where to look at in libpq/psql to
add the option.
The place to *enforce* the option is src/interfaces/libpq/fe-secure.c
(look for SSLv23_method() and SSL_CTX_set_options()). I haven't looked
into how to set it.
Hi
2014-11-26 16:46 GMT+01:00 Pavel Stehule pavel.steh...@gmail.com:
2014-11-26 13:31 GMT+01:00 Marko Tiikkaja ma...@joh.to:
On 11/26/14 8:55 AM, Pavel Stehule wrote:
* should be assertions globally enabled/disabled? - I have no personal
preference in this question.
I think so. The
Greetings,
The include_realm default for GSSAPI and SSPI is currently
'include_realm=0', meaning that the realm is stripped off of the
Kerberos principal (aka the 'system' username) prior to looking up the
user in pg_authid.
This is fine in a single-realm environment but extremely
In the pgsql-performance thread at
http://www.postgresql.org/message-id/flat/CAOR=d=3j1U_q-zf8+jUx1hkx8ps+N8pm=EUTqyFdJ5ov=+f...@mail.gmail.com
it emerged that a substantial part of the slowdown Scott saw from 8.4 to
9.2 was an unexpected consequence of the fact that the planner now
considers
On 11/26/14 2:01 PM, Stephen Frost wrote:
As such, I'd like to propose changing the default to be
'include_realm=1'.
Sounds reasonable to me.
include_realm is supported back to 8.4, so affected users can set
include_realm=0 in their existing installations.
--
Sent via pgsql-hackers
* Peter Eisentraut (pete...@gmx.net) wrote:
On 11/26/14 2:01 PM, Stephen Frost wrote:
As such, I'd like to propose changing the default to be
'include_realm=1'.
Sounds reasonable to me.
include_realm is supported back to 8.4, so affected users can set
include_realm=0 in their
On Wed, Nov 26, 2014 at 5:06 AM, Alvaro Herrera alvhe...@2ndquadrant.com
wrote:
Jeff Janes wrote:
This is what I get in the log from the attempted restart:
PST LOG: database system was interrupted; last known up at 2014-11-25
15:40:33 PST
PST LOG: database system was not properly
On 11/26/14 12:46 PM, Peter Geoghegan wrote:
On Wed, Nov 26, 2014 at 2:05 AM, Dave Page dp...@postgresql.org wrote:
You may want to bear in mind that postgres.app is on the main PG
downloads page on the website. If you're patching Postgres to add a
feature like this, it would become a fork and
On 11/26/14 9:27 AM, Alvaro Herrera wrote:
I haven't done anything about documentation. I thought a new chapter
after Additional Supplied Modules, perhaps entitled Additional Sample
Modules would be appropriate.
I would remove the SGML files and put simple README files into each
directory.
Tested on 9.4b3, 9.4rc1, 9.5devel
select * from json_to_record('
{id:1,val:josh,valry:[potter,chef,programmer]}') as r(id
int, val text, valry text[]);
ERROR: missing dimension value
With some experimentation, I can't find any way to convert a JSON array
to an array field using json_to_record
On 11/26/2014 11:54 AM, Josh Berkus wrote:
Tested on 9.4b3, 9.4rc1, 9.5devel
select * from json_to_record('
{id:1,val:josh,valry:[potter,chef,programmer]}') as r(id
int, val text, valry text[]);
ERROR: missing dimension value
With some experimentation, I can't find any way to convert
On Wed, Nov 26, 2014 at 8:01 PM, Stephen Frost sfr...@snowman.net wrote:
Greetings,
The include_realm default for GSSAPI and SSPI is currently
'include_realm=0', meaning that the realm is stripped off of the
Kerberos principal (aka the 'system' username) prior to looking up the
user
* Magnus Hagander (mag...@hagander.net) wrote:
On Wed, Nov 26, 2014 at 8:01 PM, Stephen Frost sfr...@snowman.net wrote:
This would be done for 9.5 and we would need to note it in the release
notes, of course.
I suggest we also backpatch some documentation suggesting that people
26 nov 2014 kl. 20:42 skrev Peter Eisentraut pete...@gmx.net:
(A build
option and a more explicit warning might be nice.)
In the freebsd ports, it is an option, default is off. :-)
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your
On 11/26/14 3:42 PM, Palle Girgensohn wrote:
26 nov 2014 kl. 20:42 skrev Peter Eisentraut pete...@gmx.net:
(A build
option and a more explicit warning might be nice.)
In the freebsd ports, it is an option, default is off. :-)
That's even better.
Sorry, I looked at the port sources and
Josh Berkus j...@agliodbs.com writes:
On 11/26/2014 11:54 AM, Josh Berkus wrote:
Tested on 9.4b3, 9.4rc1, 9.5devel
select * from json_to_record('
{id:1,val:josh,valry:[potter,chef,programmer]}') as r(id
int, val text, valry text[]);
ERROR: missing dimension value
With some
Hi,
On 2014-11-26 11:29:09 -0800, Jeff Janes wrote:
On Wed, Nov 26, 2014 at 5:06 AM, Alvaro Herrera alvhe...@2ndquadrant.com
wrote:
Jeff Janes wrote:
This is what I get in the log from the attempted restart:
PST LOG: database system was interrupted; last known up at 2014-11-25
On 11/26/2014 03:48 PM, Tom Lane wrote:
Arguably,
populate_record_worker should be smart enough to convert somehow, but
it isn't today. Looks to me like it wouldn't succeed for the comparable
case of converting a sub-object to a Postgres composite type, either.
I'm satisfied with regarding
* Tom Lane (t...@sss.pgh.pa.us) wrote:
As far as your request for a better error message is concerned, I'm a
bit inclined to lay the blame on array_in rather than the JSON code.
Wouldn't it be better if it said
ERROR: invalid input syntax for array: [potter,chef,programmer]
On Wed, Nov 26, 2014 at 2:00 PM, Andrew Dunstan and...@dunslane.net wrote:
The client's question is whether this is not a bug. It certainly seems like
it should be possible to plan a query without chewing up this much memory,
or at least to be able to limit the amount of memory that can be
On 26.11.2014 23:26, Peter Geoghegan wrote:
On Wed, Nov 26, 2014 at 2:00 PM, Andrew Dunstan and...@dunslane.net wrote:
The client's question is whether this is not a bug. It certainly seems like
it should be possible to plan a query without chewing up this much memory,
or at least to be able
On 11/26/2014 11:00 PM, Andrew Dunstan wrote:
Attached is some anonymized DDL for a fairly complex schema from a
PostgreSQL Experts client. Also attached is an explain query that runs
against the schema. The client's problem is that in trying to run the
explain, Postgres simply runs out
On 11/26/2014 05:26 PM, Peter Geoghegan wrote:
On Wed, Nov 26, 2014 at 2:00 PM, Andrew Dunstan and...@dunslane.net wrote:
The client's question is whether this is not a bug. It certainly seems like
it should be possible to plan a query without chewing up this much memory,
or at least to be
Stephen Frost sfr...@snowman.net writes:
* Tom Lane (t...@sss.pgh.pa.us) wrote:
As far as your request for a better error message is concerned, I'm a
bit inclined to lay the blame on array_in rather than the JSON code.
Wouldn't it be better if it said
ERROR: invalid input syntax for array:
On Mon, Nov 3, 2014 at 12:39:26PM -0800, Jeff Janes wrote:
It looked to me that the formula, when descending from a previously stressed
state, would be:
greatest(1 + checkpoint_completion_target) * checkpoint_segments,
wal_keep_segments) + 1 +
2 * checkpoint_segments + 1
I don't think
On Thu, Nov 27, 2014 at 4:29 AM, Jeff Janes jeff.ja...@gmail.com wrote:
pg_xlogdump doesn't exist yet in 9.2 (or can I use a newer one against the
older files?).
Not sure if pg_xlogdump would work (9.5 not for sure, 9.4 should
partially, 9.3 has better chances), but you could try this one as
On Fri, Nov 21, 2014 at 07:49:45AM -0600, k...@rice.edu wrote:
Hi,
This indicates that another part of the system is the resource limit,
not the CRC calculation. My money is on the I/O system. Try it using
an in memory filesystem and see if that matters. Even if it is still
the same
On Tue, Nov 25, 2014 at 9:30 PM, Jeff Janes jeff.ja...@gmail.com wrote:
Using both 9.2.9 and 9_2_STABLE 9b468bcec15f1ea7433d4, I get a fairly
reproducible startup failure.
What I was doing is restore a database from a base backup and roll it
forward with a recovery.conf until it completes
On 11/26/2014 05:00 PM, Andrew Dunstan wrote:
Attached is some anonymized DDL for a fairly complex schema from a
PostgreSQL Experts client. Also attached is an explain query that runs
against the schema. The client's problem is that in trying to run the
explain, Postgres simply runs out of
On Sat, Nov 8, 2014 at 05:56:00PM +0100, Andres Freund wrote:
On 2014-11-08 11:52:43 -0500, Tom Lane wrote:
Adding a similar
level of burden to support a feature with a narrow use-case seems like
a nonstarter from here.
I don't understand this statement. In my experience the lack of a
Bruce Momjian wrote:
On Sat, Nov 8, 2014 at 05:56:00PM +0100, Andres Freund wrote:
On 2014-11-08 11:52:43 -0500, Tom Lane wrote:
Adding a similar level of burden to support a feature with a
narrow use-case seems like a nonstarter from here.
I don't understand this statement. In my
* Alvaro Herrera (alvhe...@2ndquadrant.com) wrote:
Bruce Momjian wrote:
How would replicating DDL handle cases where the master and slave
servers have different major versions and the DDL is only supported by
the Postgres version on the master server?
Normally you would replicate between
On Wed, Nov 26, 2014 at 7:10 PM, Christoph Berg c...@df7cb.de wrote:
Re: Petr Jelinek 2014-11-25 5474efea.2040...@2ndquadrant.com
Patch committed.
Thanks!
I'm a bit late to the party, but wouldn't
recovery_target_action = ...
have been a better name for this? It'd be in line with the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 11/25/2014 12:49 PM, Tom Lane wrote:
While fooling around with the array_agg(anyarray) patch, I noted
that dblink_get_connections() returns NULL if there are no active
connections. It seems like an empty array might be a saner
definition
1 - 100 of 108 matches
Mail list logo
