On 25.04.2012 18:49, Robert Haas wrote:
Maybe this is a silly idea, but if you're thinking about creating a
local XID space and a global XID space, it might be a good idea to
also make allowance for an unlogged XID space - that is, an XID
space that is global to all backends but need not survive
On Thu, Apr 26, 2012 at 1:35 AM, Jameison Martin jameis...@yahoo.com wrote:
Tom, I whipped up some INSERT/SELECT tests where I selected into a
temporary table as you suggested. The target temporary table and the source
table were in cache and I basically disabled things that would cause noise.
On Wed, Apr 25, 2012 at 7:34 PM, Robert Haas robertmh...@gmail.com wrote:
On Wed, Apr 25, 2012 at 1:31 PM, Simon Riggs si...@2ndquadrant.com wrote:
However, it is a fallacy that this is a good solution for using temp
tables on HS. I think the wish to enhance Oracle compatibility is
making some
On Thu, Apr 26, 2012 at 5:57 AM, Robert Haas robertmh...@gmail.com wrote:
On Wed, Apr 25, 2012 at 10:04 PM, Noah Misch n...@leadboat.com wrote:
Based on the range of assessments spanning your almost useless to Merlin's
killer feature, I gather that its utility is exceptionally site-specific.
Robert Haas wrote:
Noah Misch wrote:
Based on the range of assessments spanning your almost useless
to Merlin's killer feature, I gather that its utility is
exceptionally site-specific.
Well said, sir.
+1
I find it a rather elegant and well-thought-out kludge.
Global temporary
On Thu, Apr 26, 2012 at 3:56 AM, Simon Riggs si...@2ndquadrant.com wrote:
Previous discussions had Tom proposing ways of extending catalogs to
allow exactly this. So designs that address that point are already on
record.
Link?
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The
Hi,
PFA test case. It used simple select statement to retrieve data via
plpython. It crashes latest pg 9.2 with the following stack trace i.e.
#0 0x0073021f in pfree ()
#1 0x7fa74b632f7a in PLy_result_dealloc () from
/home/masif/work/postgresql/postgresql/inst/lib/plpython2.so
FYI,
I have observed this crash on Linux64. Thanks.
Best Regards,
Muhammad Asif Naeem
On Thu, Apr 26, 2012 at 5:32 PM, Asif Naeem asif.na...@enterprisedb.comwrote:
Hi,
PFA test case. It used simple select statement to retrieve data via
plpython. It crashes latest pg 9.2 with the following
I'm beginning to work on advanced additions to in-core replication for
PostgreSQL.
There are a number of additional features for existing single-master
replication still to achieve, but the key topics to be addressed are
major leaps forward in functionality. I hope to add useful features in
9.3,
On Thu, Apr 26, 2012 at 12:49 PM, Kevin Grittner
kevin.gritt...@wicourts.gov wrote:
So, I can't help wonder if what we're really missing here is a
high-performance, log-based logical replication solution with good
core support.
On that, we do agree completely. That is exactly my goal for 9.3.
On Thu, Apr 26, 2012 at 12:49 PM, Kevin Grittner
kevin.gritt...@wicourts.gov wrote:
I find it a rather elegant and well-thought-out kludge.
Global temporary tables as a feature are far more than a kludge; I
assume you're talking about that feature as a solution for the no
temporary tables on
On Wed, Apr 25, 2012 at 9:28 AM, Merlin Moncure mmonc...@gmail.com wrote:
That patch actually has more than one optimization in it, I think, but
the basic idea is that if we could figure out a way to set
HEAP_XMIN_COMMITTED when loading data into a table created or
truncated within the same
On Thu, Apr 26, 2012 at 8:27 AM, Simon Riggs si...@2ndquadrant.com wrote:
The source table had 5 integer columns, and was populated with 10 million
rows.
...
2) target has all nullable columns, only the first column is set: the
patch was slightly faster
...
By slightly faster I'm talking on
On Thu, Apr 26, 2012 at 9:18 AM, Simon Riggs si...@2ndquadrant.com wrote:
Implementing a feature that *requires* those things is madness and
obscuring those crucial points is not balanced or fair.
I think this whole discussion started the wrong way around. If the
goal of implementing GTTs is to
On Thu, Apr 26, 2012 at 1:41 PM, Simon Riggs si...@2ndquadrant.com wrote:
I will also be organising a small-medium sized Future of In-Core
Replication meeting in Ottawa on Wed 16 May, 6-10pm.
Thanks for such rapid response. I've put up a wiki page and will be
adding names as they come through
On Thu, Apr 26, 2012 at 9:57 AM, Greg Stark st...@mit.edu wrote:
On Thu, Apr 26, 2012 at 9:18 AM, Simon Riggs si...@2ndquadrant.com wrote:
Implementing a feature that *requires* those things is madness and
obscuring those crucial points is not balanced or fair.
I think this whole discussion
Robert Haas robertmh...@gmail.com writes:
On Thu, Apr 26, 2012 at 3:56 AM, Simon Riggs si...@2ndquadrant.com wrote:
Previous discussions had Tom proposing ways of extending catalogs to
allow exactly this. So designs that address that point are already on
record.
Link?
There was a thread a
On Thu, Apr 26, 2012 at 10:12 AM, Tom Lane t...@sss.pgh.pa.us wrote:
Robert Haas robertmh...@gmail.com writes:
On Thu, Apr 26, 2012 at 3:56 AM, Simon Riggs si...@2ndquadrant.com wrote:
Previous discussions had Tom proposing ways of extending catalogs to
allow exactly this. So designs that
On Thu, Apr 26, 2012 at 3:40 PM, Kevin Grittner
kevin.gritt...@wicourts.gov wrote:
[resending because of postgresql.org bounces on first try]
Simon Riggs si...@2ndquadrant.com wrote:
Kevin Grittner kevin.gritt...@wicourts.gov wrote:
The GSoC xReader project is intended to be a major step
On Wed, Apr 25, 2012 at 7:59 PM, Robert Haas robertmh...@gmail.com wrote:
On Wed, Apr 25, 2012 at 2:48 PM, Tom Lane t...@sss.pgh.pa.us wrote:
Bruce Momjian br...@momjian.us writes:
I had hoped to complete the release notes by March 30, but travel and
catching up on old stuff has delayed that.
I'm getting an assertion failure on a fresh git checkout with this query:
create table foo (a int4, b text);CREATE TABLE
create index i_foo on foo (b, a);CREATE INDEX
select * from foo where a = 0 and (b = 'foo' or b = 'bar');
TRAP: FailedAssertion(!(const Node*)(ipath))-type) ==
On Thu, Apr 26, 2012 at 01:26:16AM -0400, Tom Lane wrote:
Bruce Momjian br...@momjian.us writes:
On Wed, Apr 25, 2012 at 05:09:04PM -0400, Tom Lane wrote:
--details-after Show branch and author info after the commit description
I don't understand the point of that.
The release notes
On 26 April 2012 17:32, Heikki Linnakangas
heikki.linnakan...@enterprisedb.com wrote:
I'm getting an assertion failure on a fresh git checkout with this query:
create table foo (a int4, b text);CREATE TABLE
create index i_foo on foo (b, a);CREATE INDEX
select * from foo where a = 0 and (b =
On Thu, Apr 26, 2012 at 1:26 AM, Tom Lane t...@sss.pgh.pa.us wrote:
Bruce Momjian br...@momjian.us writes:
On Wed, Apr 25, 2012 at 05:09:04PM -0400, Tom Lane wrote:
--details-after Show branch and author info after the commit description
I don't understand the point of that.
The release
On Thu, Apr 26, 2012 at 11:02 AM, Simon Riggs si...@2ndquadrant.com wrote:
On Thu, Apr 26, 2012 at 3:40 PM, Kevin Grittner
kevin.gritt...@wicourts.gov wrote:
[resending because of postgresql.org bounces on first try]
Simon Riggs si...@2ndquadrant.com wrote:
Kevin Grittner
On Thu, Apr 26, 2012 at 18:56, Robert Haas robertmh...@gmail.com wrote:
On Thu, Apr 26, 2012 at 1:26 AM, Tom Lane t...@sss.pgh.pa.us wrote:
Bruce Momjian br...@momjian.us writes:
On Wed, Apr 25, 2012 at 05:09:04PM -0400, Tom Lane wrote:
--details-after Show branch and author info after the
On Thu, Apr 26, 2012 at 06:59:18PM +0200, Magnus Hagander wrote:
On Thu, Apr 26, 2012 at 18:56, Robert Haas robertmh...@gmail.com wrote:
On Thu, Apr 26, 2012 at 1:26 AM, Tom Lane t...@sss.pgh.pa.us wrote:
Bruce Momjian br...@momjian.us writes:
On Wed, Apr 25, 2012 at 05:09:04PM -0400, Tom
On Thu, Apr 26, 2012 at 5:57 PM, Robert Haas robertmh...@gmail.com wrote:
On Thu, Apr 26, 2012 at 11:02 AM, Simon Riggs si...@2ndquadrant.com wrote:
On Thu, Apr 26, 2012 at 3:40 PM, Kevin Grittner
kevin.gritt...@wicourts.gov wrote:
[resending because of postgresql.org bounces on first try]
Heikki Linnakangas heikki.linnakan...@enterprisedb.com writes:
I'm getting an assertion failure on a fresh git checkout with this query:
create table foo (a int4, b text);CREATE TABLE
create index i_foo on foo (b, a);CREATE INDEX
select * from foo where a = 0 and (b = 'foo' or b = 'bar');
Bruce Momjian br...@momjian.us writes:
I agree adding rarely-used options to a tool doesn't make sense, but the
question is what percentage of the git_changelog userbase am I?
50% I think. The only thing that's really concerning me here is that
the reverse-sort option seems likely to be
The GSoC xReader project is intended to be a major step toward
that, by providing a way to translate the WAL stream to a series
of notifications of logical events to clients which register with
xReader.
sigh Yes, it appears very similar. I didn't know about this.
This isn't a problem. In
On mån, 2012-04-23 at 02:25 +0200, Jan Urbański wrote:
It turned out not to be as straightforward as I though :(
Yeah, been there ...
The I/O code in PL/Python is a bit of a mess and that's something that
I'd like to address somewhere in the 9.3 development cycle. Right now
making the
On mån, 2012-04-23 at 12:30 -0400, Noah Misch wrote:
I've been enjoying \x auto in .psqlrc, but I noticed the row count footer
missing when it chooses ordinary output:
Looks like the logic in printQuery() needs further treatment.
Hmm, this looks a bit tricky, because at the time we add the
I came across this comment:
/*
* ExceptionalCondition - Handles the failure of an Assert()
*
* Note: this can't actually return, but we declare it as returning int
* because the TrapMacro() macro might get wonky otherwise.
*/
But it seems to me that this can easily be fixed like shown
On 4/26/12 7:41 AM, Simon Riggs wrote:
5. WRITE-SCALEABLE - the ability to partition data across nodes in a
way that allows the solution to improve beyond the write rate of a
single node.
It would be valuable to look at READ-SCALEABLE as well; specifically a second form of
synchronous
On Thu, Apr 26, 2012 at 2:05 PM, Tom Lane t...@sss.pgh.pa.us wrote:
Bruce Momjian br...@momjian.us writes:
I agree adding rarely-used options to a tool doesn't make sense, but the
question is what percentage of the git_changelog userbase am I?
50% I think. The only thing that's really
Simon and Greg,
The math on space savings is assuming that columns will be used roughly from
first to last as declared in the DDL, not a random distribution of column
values. This is the case for the particular schema that I'm looking at. I'm not
asserting that it is the common case in
Peter Eisentraut pete...@gmx.net writes:
I came across this comment:
/*
* ExceptionalCondition - Handles the failure of an Assert()
*
* Note: this can't actually return, but we declare it as returning int
* because the TrapMacro() macro might get wonky otherwise.
*/
But it seems to
On 04/26/2012 02:54 PM, Robert Haas wrote:
On Thu, Apr 26, 2012 at 2:05 PM, Tom Lanet...@sss.pgh.pa.us wrote:
Bruce Momjianbr...@momjian.us writes:
I agree adding rarely-used options to a tool doesn't make sense, but the
question is what percentage of the git_changelog userbase am I?
50%
On Thu, Apr 26, 2012 at 02:05:23PM -0400, Tom Lane wrote:
Bruce Momjian br...@momjian.us writes:
I agree adding rarely-used options to a tool doesn't make sense, but the
question is what percentage of the git_changelog userbase am I?
50% I think. The only thing that's really concerning me
Simon,
So the idea is that you'll present briefly your intentions for 9.3 at
the developer meeting, and then have this in-depth afterwards? Sounds
great.
--
Josh Berkus
PostgreSQL Experts Inc.
http://pgexperts.com
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make
On Thu, Apr 26, 2012 at 6:48 PM, Josh Berkus j...@agliodbs.com wrote:
So the idea is that you'll present briefly your intentions for 9.3 at
the developer meeting, and then have this in-depth afterwards? Sounds
great.
I really, really do not want the developer meeting to turn into a
series of
On Mon, Apr 16, 2012 at 4:13 PM, Robert Haas robertmh...@gmail.com wrote:
But fundamentally we all seem to be converging on some variant of the
soft conflict idea.
So, as a first step, I've committed a patch that just throws a hard
conflict. I think we probably want to optimize this further,
Simon,
I'm beginning to work on advanced additions to in-core replication for
PostgreSQL.
...
Those are the basic requirements that I am trying to address. There
are a great many important details, but the core of this is probably
what I would call logical replication, that is shipping
Tom,
I can't help thinking that (a) this is an incredibly narrow use-case,
and (b) you'd be well advised to rethink your schema design anyway.
It's more common than you'd think. Both EAV and Hstore have their own
(severe) drawbacks.
For example, I'm working on an application which collects
45 matches
Mail list logo
