On Aug 15, 2013 3:44 AM, Tom Lane t...@sss.pgh.pa.us wrote:
Josh Berkus j...@agliodbs.com writes:
Before 9.3, it would delete one specific file from a potentially shared
directory. In 9.3 it deletes the entire contents of a potentially
shared
directory. That is a massive expansion in the
psql is missing tab completion for \dx (or more usfully, for \dx+).
Attached patch fixes this.
Do we consider this a bugfix and backpatch (at least to 9.3? even
though the problem goes back further), or head only?
--
Magnus Hagander
Me: http://www.hagander.net/
Work:
I wrote:
I've reworked on the patch.
Attached is an updated version of the patch. In that version the code for the
newly added function build_function_pathkeys() has been made more simple by
using the macro INTEGER_BTREE_FAM_OID.
Thanks,
Best regards,
Etsuro Fujita
ordinality-path-20130815
On Wed, Aug 14, 2013 at 9:34 PM, Peter Eisentraut pete...@gmx.net wrote:
On Tue, 2013-08-13 at 14:30 -0700, Josh Berkus wrote:
Currently PL/python has 1 dimension hardcoded for returning arrays:
create or replace function nparr ()
returns float[][]
language plpythonu
as $f$
from numpy
Magnus Hagander mag...@hagander.net writes:
psql is missing tab completion for \dx (or more usfully, for \dx+).
Attached patch fixes this.
Do we consider this a bugfix and backpatch (at least to 9.3? even
though the problem goes back further), or head only?
Sounds like a feature to me. I
* Tom Lane (t...@sss.pgh.pa.us) wrote:
Magnus Hagander mag...@hagander.net writes:
psql is missing tab completion for \dx (or more usfully, for \dx+).
Attached patch fixes this.
Do we consider this a bugfix and backpatch (at least to 9.3? even
though the problem goes back further), or
On Thu, Aug 15, 2013 at 5:26 PM, Stephen Frost sfr...@snowman.net wrote:
* Tom Lane (t...@sss.pgh.pa.us) wrote:
Magnus Hagander mag...@hagander.net writes:
psql is missing tab completion for \dx (or more usfully, for \dx+).
Attached patch fixes this.
Do we consider this a bugfix and
There is no way to know how many dimensions the function expects to get
back. (float[][] doesn't actually mean anything.) So when converting
the return value back to SQL, you'd have to guess, is the first element
convertible to float (how do you know?), if not, does it support the
sequence
On 08/13/2013 07:16 PM, Peter Eisentraut wrote:
My next best idea is CREATE TRANSFORM FOR hstore SERVER LANGUAGE plperl,
which preserves the overall idea but still distinguishes server from
client languages.
Comments?
My thinking is that TRANSFORMS will almost certainly be managed by
Where are we on this issue?
I've been able to replicate it pretty easily with PostgreSQL and
continue to look into it. I've contacted Theodore Ts'o and have gotten
some useful information, however I'm unable to replicate the behavior
with the test program (even one that's been modified). What
Apologies, but this sub-thread got lost when I changed email
accounts. I found it in a final review to make sure nothing had
fallen through the cracks.
Noah Misch n...@leadboat.com wrote:
On Thu, Jan 24, 2013 at 01:09:28PM -0500, Noah Misch wrote:
There's no documented support for table
Taking a look at PostgreSQL HEAD today, I noticed that pg_ctl
documents that pg_ctl initdb takes OPTIONS but doesn't document them
(unlike for start and others).
Is this intentional?
--
Jon
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your
On 08/16/2013 10:44 AM, Vlad Arkhipov wrote:
On 08/15/2013 03:27 AM, Jim Nasby wrote:
On 8/14/13 12:31 AM, Vlad Arkhipov wrote:
I used to use VACUUM FULL periodically to resolve the issue, but the
problem arises again in 2-3 months.
Here is the statistics (from pgstattuple). I run VACUUM FULL
On 08/15/2013 05:06 AM, Sergey Konoplev wrote:
On Tue, Aug 13, 2013 at 10:31 PM, Vlad Arkhipov arhi...@dc.baikal.ru wrote:
I used to use VACUUM FULL periodically to resolve the issue, but the problem
arises again in 2-3 months.
Here is the statistics (from pgstattuple). I run VACUUM FULL on
Hi,
While testing performance of PG9.2.4 using DBT5, I am getting error in
dbt5_output_result/bh/bh.out file as :
*BrokerageHouseMain: symbol lookup error: BrokerageHouseMain: undefined symbol:
PQescapeLiteral*
So i tried with CPP code as follow
-- test.cpp
amul sul sul_a...@yahoo.co.in writes:
While testing performance of PG9.2.4 using DBT5, I am getting error inÂ
*BrokerageHouseMain: symbol lookup error: BrokerageHouseMain: undefined
symbol: PQescapeLiteral*
You're linking against a pre-9.0 copy of libpq.so.
regards,
16 matches
Mail list logo
