On 30 August 2012 20:05, Robert Haas robertmh...@gmail.com wrote:
On Sun, Aug 12, 2012 at 5:14 PM, Dean Rasheed dean.a.rash...@gmail.com
wrote:
None of this new code kicks in for non-security barrier views, so the
kinds of plans I posted upthread remain unchanged in that case. But
now a
When a cascading standby launches a new walsender, it fetches the
current recovery timeline:
/*
* Use the recovery target timeline ID during recovery
*/
if (am_cascading_walsender)
ThisTimeLineID = GetRecoveryTargetTLI();
Comment in
2012/6/21 Simon Riggs si...@2ndquadrant.com:
On 21 June 2012 19:13, Jaime Casanova ja...@2ndquadrant.com wrote:
On Sun, Jun 10, 2012 at 4:15 AM, Kohei KaiGai kai...@kaigai.gr.jp wrote:
2012/6/8 Simon Riggs si...@2ndquadrant.com:
I have a prototype that has some of these characteristics, so I
On Fri, Aug 31, 2012 at 4:07 AM, Peter Eisentraut pete...@gmx.net wrote:
psql has supported older servers for a great while now, so this sort of
things seems pretty useless now:
psql (9.2rc1, server 9.1.4)
WARNING: psql version 9.2, server version 9.1.
Some psql features might not work
I
Robert Haas robertmh...@gmail.com writes:
I guess I don't particularly like either of these changes. The first
Fair enough.
one is mostly harmless, but I don't really see why it's any better,
and it does have the downside of traversing the string twice (once for
strlen and a second time in
On Aug 28, 2012 9:59 PM, Tom Lane t...@sss.pgh.pa.us wrote:
Magnus Hagander mag...@hagander.net writes:
On Tue, Aug 28, 2012 at 6:42 PM, Tom Lane t...@sss.pgh.pa.us wrote:
I don't see anything particularly incorrect about that. The point of
the --verbose switch is to track what pg_dump is
Pavel Stehule pavel.steh...@gmail.com writes:
a motivation for this patch was discussion about parametrised DO
statement - and simple possibility of access to host variables (psql)
variables from server - PL scripts.
Pavel, you didn't say what you think about the WITH FUNCTION proposal?
And
2012/8/31 Dimitri Fontaine dimi...@2ndquadrant.fr:
Pavel Stehule pavel.steh...@gmail.com writes:
a motivation for this patch was discussion about parametrised DO
statement - and simple possibility of access to host variables (psql)
variables from server - PL scripts.
Pavel, you didn't say
Hi,
is there any way to check if row have already been modified by the current
transaction? I tried condition txid_current() = xmin, but there is problem
with the savepoints. After every savepoint rows are getting higher xmin
values, but txid_current() remains the same.
Regards,
Miroslav
Hi Robert,
there is a note in the pg documentation chapter
12.6.5 Ispell Dictionary
*Note:*MySpell does not support compound words. Hunspell has
sophisticated support for compound words. At present, PostgreSQL
implements only the basic compound word operations of Hunspell.
Regards
Was there any conclusion from these ideas?
---
On Wed, Aug 1, 2012 at 11:35:56AM -0400, Robert Haas wrote:
On Wed, Aug 1, 2012 at 10:12 AM, Tom Lane t...@sss.pgh.pa.us wrote:
I think you may be right that using __asm__
On 08/24/2012 11:44 AM, Alvaro Herrera wrote:
Again, win32 testing would be welcome. Sadly, buildfarm does not run
pg_upgrade's make check.
Yesterday I added a new module to the buildfarm client code to run this
I've added this to the release blockers section for 9.2 on the wiki,
as without it, pl/perl is unusable on Win32.
On Thu, Aug 30, 2012 at 1:39 PM, Dave Page dp...@pgadmin.org wrote:
On Thu, Aug 30, 2012 at 6:34 AM, Owais Khan owais.k...@enterprisedb.com
wrote:
Hello,
We are getting crash
On 08/31/2012 11:05 AM, Dave Page wrote:
I've added this to the release blockers section for 9.2 on the wiki,
as without it, pl/perl is unusable on Win32.
I'll have a look at it today.
cheers
andrew
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes
On Fri, Aug 31, 2012 at 4:10 PM, Andrew Dunstan and...@dunslane.net wrote:
On 08/31/2012 11:05 AM, Dave Page wrote:
I've added this to the release blockers section for 9.2 on the wiki,
as without it, pl/perl is unusable on Win32.
I'll have a look at it today.
Thanks Andrew - minor
On 08/31/2012 11:14 AM, Dave Page wrote:
On Fri, Aug 31, 2012 at 4:10 PM, Andrew Dunstan and...@dunslane.net wrote:
On 08/31/2012 11:05 AM, Dave Page wrote:
I've added this to the release blockers section for 9.2 on the wiki,
as without it, pl/perl is unusable on Win32.
I'll have a look at
On Fri, Aug 31, 2012 at 4:57 PM, Andrew Dunstan and...@dunslane.net wrote:
On 08/31/2012 11:14 AM, Dave Page wrote:
On Fri, Aug 31, 2012 at 4:10 PM, Andrew Dunstan and...@dunslane.net
wrote:
On 08/31/2012 11:05 AM, Dave Page wrote:
I've added this to the release blockers section for 9.2
On 08/31/2012 10:52 AM, Andrew Dunstan wrote:
On 08/24/2012 11:44 AM, Alvaro Herrera wrote:
Again, win32 testing would be welcome. Sadly, buildfarm does not run
pg_upgrade's make check.
Yesterday I added a new module to the buildfarm client code to run
this
On Fri, Aug 31, 2012 at 5:18 PM, Dave Page dp...@pgadmin.org wrote:
On Fri, Aug 31, 2012 at 4:57 PM, Andrew Dunstan and...@dunslane.net wrote:
On 08/31/2012 11:14 AM, Dave Page wrote:
On Fri, Aug 31, 2012 at 4:10 PM, Andrew Dunstan and...@dunslane.net
wrote:
On 08/31/2012 11:05 AM, Dave
Tom Lane t...@sss.pgh.pa.us writes:
Or maybe we should disable event triggers altogether in standalone mode?
Would something as simple as the attached work for doing that? (passes
make check and I did verify manually that postmaster --single is happy
with it and skipping Event Triggers).
On 08/31/2012 12:18 PM, Dave Page wrote:
On Fri, Aug 31, 2012 at 4:57 PM, Andrew Dunstan and...@dunslane.net wrote:
On 08/31/2012 11:14 AM, Dave Page wrote:
On Fri, Aug 31, 2012 at 4:10 PM, Andrew Dunstan and...@dunslane.net
wrote:
On 08/31/2012 11:05 AM, Dave Page wrote:
I've added this to
On Fri, Aug 31, 2012 at 5:37 PM, Andrew Dunstan and...@dunslane.net wrote:
On 08/31/2012 12:18 PM, Dave Page wrote:
On Fri, Aug 31, 2012 at 4:57 PM, Andrew Dunstan and...@dunslane.net
wrote:
On 08/31/2012 11:14 AM, Dave Page wrote:
On Fri, Aug 31, 2012 at 4:10 PM, Andrew Dunstan
On 08/31/2012 12:41 PM, Dave Page wrote:
On Fri, Aug 31, 2012 at 5:37 PM, Andrew Dunstan and...@dunslane.net wrote:
On 08/31/2012 12:18 PM, Dave Page wrote:
On Fri, Aug 31, 2012 at 4:57 PM, Andrew Dunstan and...@dunslane.net
wrote:
On 08/31/2012 11:14 AM, Dave Page wrote:
On Fri, Aug 31,
On Fri, Aug 31, 2012 at 5:51 PM, Andrew Dunstan and...@dunslane.net wrote:
On 08/31/2012 12:41 PM, Dave Page wrote:
On Fri, Aug 31, 2012 at 5:37 PM, Andrew Dunstan and...@dunslane.net
wrote:
On 08/31/2012 12:18 PM, Dave Page wrote:
On Fri, Aug 31, 2012 at 4:57 PM, Andrew Dunstan
On Fri, Aug 31, 2012 at 5:03 PM, Heikki Linnakangas hlinn...@iki.fi wrote:
When a cascading standby launches a new walsender, it fetches the current
recovery timeline:
/*
* Use the recovery target timeline ID during recovery
*/
if (am_cascading_walsender)
Pavel Stehule pavel.steh...@gmail.com writes:
Pavel, you didn't say what you think about the WITH FUNCTION proposal?
I don't like it - this proposal is too lispish - it is not SQL
We're not doing lambda here, only extending a facility that we rely on
today. The function would be named, for
On 08/31/2012 01:10 PM, Dave Page wrote:
On Fri, Aug 31, 2012 at 5:51 PM, Andrew Dunstan and...@dunslane.net wrote:
On 08/31/2012 12:41 PM, Dave Page wrote:
On Fri, Aug 31, 2012 at 5:37 PM, Andrew Dunstan and...@dunslane.net
wrote:
On 08/31/2012 12:18 PM, Dave Page wrote:
On Fri, Aug 31,
2012/8/31 Dimitri Fontaine dimi...@2ndquadrant.fr:
Pavel Stehule pavel.steh...@gmail.com writes:
Pavel, you didn't say what you think about the WITH FUNCTION proposal?
I don't like it - this proposal is too lispish - it is not SQL
We're not doing lambda here, only extending a facility that
Dave Page dp...@pgadmin.org writes:
As a side note - I'm not sure why _USE_32BIT_TIME_T was removed in the
first place; it was added specifically to avoid this sort of problem,
though iirc at the time we were thinking of extensions like Slony and
PostGIS being built with Mingw for use with the
On Fri, Aug 31, 2012 at 4:59 AM, Magnus Hagander mag...@hagander.net wrote:
On Fri, Aug 31, 2012 at 4:07 AM, Peter Eisentraut pete...@gmx.net wrote:
psql has supported older servers for a great while now, so this sort of
things seems pretty useless now:
psql (9.2rc1, server 9.1.4)
WARNING:
On Thu, Aug 30, 2012 at 5:55 PM, Tomas Vondra t...@fuzzy.cz wrote:
It does, but AFAIK the -l means logging. I suppose
--aggregate-interval would be a good option name, I don't see a reason
to put there the additional word when there are other aggregated values
(e.g. num of transactions).
Oh,
On 08/31/2012 03:36 PM, Tom Lane wrote:
Dave Page dp...@pgadmin.org writes:
As a side note - I'm not sure why _USE_32BIT_TIME_T was removed in the
first place; it was added specifically to avoid this sort of problem,
though iirc at the time we were thinking of extensions like Slony and
PostGIS
Andrew Dunstan and...@dunslane.net writes:
I'm not sure what we need to do to progress on this, especially re the
back branches.
The calendar might help us here. 9.2 is due to wrap next week, but it
will likely be a couple of months before we contemplate new back-branch
releases. So we
On 08/31/2012 06:39 PM, Tom Lane wrote:
Andrew Dunstan and...@dunslane.net writes:
I'm not sure what we need to do to progress on this, especially re the
back branches.
The calendar might help us here. 9.2 is due to wrap next week, but it
will likely be a couple of months before we
On Thu, Aug 30, 2012 at 1:25 PM, Peter Geoghegan pe...@2ndquadrant.com wrote:
Just how helpful is effective_io_concurrency? Did someone produce a
benchmark at some point?
Attached is a benchmark I put together a while ago.
I don't know how close to real world it might be. I haven't seen it
When initializing a large database, pgbench writes tons of %d tuples
done lines. I propose to change this to a sort of progress counter
that stays on the same line, as in the attached patch.
diff --git a/contrib/pgbench/pgbench.c b/contrib/pgbench/pgbench.c
index 00cab73..b5f3054 100644
---
As implemented in HEAD, LATERAL means to run a nestloop in which the
lateral-referencing query is run once per row of the referenced table,
and the resulting rows are joined to just that row of the referenced
table. So for example:
# select * from (values (2),(4)) v(x), lateral
Merlin Moncure mmonc...@gmail.com writes:
This is just awesome. Anyways, I was looking around the docs for
references to the old methodology of select list SRF function calls.
This paragraph:
http://www.postgresql.org/docs/devel/static/xfunc-sql.html#XFUNC-SQL-FUNCTIONS-RETURNING-SET
could
2012/9/1 Tom Lane t...@sss.pgh.pa.us:
As implemented in HEAD, LATERAL means to run a nestloop in which the
lateral-referencing query is run once per row of the referenced table,
and the resulting rows are joined to just that row of the referenced
table. So for example:
# select * from
39 matches
Mail list logo
