On 22/08/12 10:56, Kevin Grittner wrote:
Josh Berkus wrote:
First, note the change in topic.
This whole discussion has gone rather far afield from Miroslav's
original submission, which was for temporal tables, which is NOT
the same thing as audit logs, although the use cases overlap
signifi
>> Large objects are limited to 2 GB in size, so a 64-bit API doesn't sound
>> very useful to me at the moment.
>
> Not entirely. pg_largeobject.pageno is int32, but that's still 2G pages
> not bytes, so there's three or so orders of magnitude that could be
> gotten by expanding the client-side A
Peter Eisentraut writes:
> On Wed, 2012-08-22 at 07:27 +0900, Tatsuo Ishii wrote:
>> I found this in the TODO list:
>> Add API for 64-bit large object access
>> If this is a still valid TODO item and nobody is working on this, I
>> would like to work in this.
> Large objects are limited to 2 GB
On Wed, 2012-08-22 at 07:27 +0900, Tatsuo Ishii wrote:
> I found this in the TODO list:
>
> Add API for 64-bit large object access
>
> If this is a still valid TODO item and nobody is working on this, I
> would like to work in this.
Large objects are limited to 2 GB in size, so a 64-bit API d
> As the maintainer of software that does multi-master, I'm a little
> confused as to why we would extend pg_bench to do this. The software
> in question should be doing the testing itself, ideally via
> it's test suite (i.e. "make test"). Having pg_bench do any of this
> would be at best a ver
-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
> The point of this functionality is to test some cluster
> software which have a capability to create multi-master
> configuration.
As the maintainer of software that does multi-master, I'm a little
confused as to why we would extend pg_ben
From: Jesper Krogh [mailto:jes...@krogh.cc]
Sent: Wednesday, August 22, 2012 1:13 AM
On 21/08/12 16:57, Amit kapila wrote:
>>Test results:
>>1. The pgbench test run for 10min.
>> 2. The test reult is for modified pgbench (such that total row size is
1800 and updated columns are of length 300)
Thanks again, the reason is found.
The following statement frees all the context for aggregation, including the
transValue and tempTransValue:
MemoryContextResetAndDeleteChildren(winstate->aggcontext);
-Original Message-
From: Tom Lane [mailto:t...@sss.pgh.pa.us]
Sent: 2012年8月22日 9:4
>> I do not intended to implement such a feature. As I wrote in the
>> subject line, I intended to enhance pgbench for "multi-master"
>> configuration. IMO, any node on multi-master configuration should
>> accept *any* queries, not only read queries but write queries. So bare
>> PostgreSQL streamin
Tatsuo Ishii writes:
>> Well, my concern here is that it's *not* going to be simple. By the
>> time we get done adding enough switches to control connection to N
>> different hosts (possibly with different usernames, passwords, etc),
>> then adding frammishes to control which scripts get sent to
"Wang, Chaoyong" writes:
> I used the function datumCopy as following:
> peraggstate->transValue = datumCopy(peraggstate->tempTransValue,
> peraggstate->transtypeByVal, peraggstate->transtypeLen);
You need to guard that with an is-null check, because datumCopy isn't
designed to cope with null va
>> What does "propagation of the writes" mean?
>
> I apologize for not being clear. In a multi-master system, people
> frequently wish to know how quickly a write operation has been
> duplicated to the other nodes. In some sense, those write operations
> are incomplete until they have happened o
Hi,
I'm trying to reduce the re-computing of window aggregation. Here the
AVG function for example.
The original window aggregation's transition value(transValue) of AVG is
an ArrayType, that contains two main values(sum, count).
Now, I'm using a temporary transition value (tempTransVa
> Well, my concern here is that it's *not* going to be simple. By the
> time we get done adding enough switches to control connection to N
> different hosts (possibly with different usernames, passwords, etc),
> then adding frammishes to control which scripts get sent to which hosts,
> and so on,
On Wed, Aug 22, 2012 at 06:26:00AM +0900, Tatsuo Ishii wrote:
> >> I am thinking about to implement "multi-master" option for pgbench.
> >> Supose we have multiple PostgreSQL running on host1 and host2.
> >> Something like "pgbench -c 10 -h host1,host2..." will create 5
> >> connections to host1 an
Tatsuo Ishii writes:
>> Why wouldn't you just fire up several copies of pgbench, one per host?
> Well, more convenient. Aside from bottle neck discussion below, simple
> tool to generate load is important IMO.
Well, my concern here is that it's *not* going to be simple. By the
time we get done
Josh Berkus wrote:
> First, note the change in topic.
>
> This whole discussion has gone rather far afield from Miroslav's
> original submission, which was for temporal tables, which is NOT
> the same thing as audit logs, although the use cases overlap
> significantly.
I don't think the conce
> Why wouldn't you just fire up several copies of pgbench, one per host?
Well, more convenient. Aside from bottle neck discussion below, simple
tool to generate load is important IMO. It will help developers to
enhance multi-master configuration in finding bugs and problems if
any. IMO I saw simil
First, note the change in topic.
This whole discussion has gone rather far afield from Miroslav's
original submission, which was for temporal tables, which is NOT the
same thing as audit logs, although the use cases overlap significantly.
Miroslav, I know this has been hard to follow, but you're
Hi,
I found this in the TODO list:
Add API for 64-bit large object access
If this is a still valid TODO item and nobody is working on this, I
would like to work in this.
--
Tatsuo Ishii
SRA OSS, Inc. Japan
English: http://www.sraoss.co.jp/index_en.php
Japanese: http://www.sraoss.co.jp
--
S
Alvaro Herrera wrote:
> I think there would need to be a way to also list transactions
> which are "in progress" -- this would include not only live
> transactions, but also all those transactions that have actually
> committed but are not yet listed as committed because their
> position in the
Gavin Flower wrote:
> So if I understand correctly...
>
> If there is a very long running transaction, say 1 hour, then all
> (or just some? - depending) transactions that nominally start and
> finish within that time, can not have definitive start times until
> the very long running transactio
Excerpts from Gavin Flower's message of mar ago 21 16:51:57 -0400 2012:
> On 22/08/12 02:16, Kevin Grittner wrote:
> > So, if you want to allow serializable temporal queries, the timing
> > of a read-write serializable transaction can't be locked down until
> > all overlapping read-write serializa
Hi all,
I've been investigating an issue with our PostgreSQL 9.1.1 (Linux x86-64
CentOS 5.8) database where restartpoints suddenly stop being generated on
the slave after working correctly for a week or two. The symptom of the
problem is that the pg_xlog directory on the slave doesn't get cleaned
On 22/08/12 02:16, Kevin Grittner wrote:
Jeff Davis wrote:
On Mon, 2012-08-20 at 19:32 -0500, Kevin Grittner wrote:
Josh Berkus wrote:
This is sounding like a completely runaway spec on what should
be a simple feature.
I hate to contribute to scope creep (or in this case scope
screami
>> I am thinking about to implement "multi-master" option for pgbench.
>> Supose we have multiple PostgreSQL running on host1 and host2.
>> Something like "pgbench -c 10 -h host1,host2..." will create 5
>> connections to host1 and host2 and send queries to host1 and host2.
>> The point of this func
Hi all,
I've been investigating an issue with our PostgreSQL 9.1.1 (Linux x86-64
CentOS 5.8) database where restartpoints suddenly stop being generated on
the streaming-replication slave after working correctly for a week or two.
The symptom of the problem is that the pg_xlog directory on the sla
On Tue, Aug 21, 2012 at 12:14 PM, Nils Goroll wrote:
> I am reviewing this one year old change again before backporting it to 9.1.3
> for production use.
>
> ATM, I believe the code is correct, but I don't want to miss the change to
> spot possible errors, so please let me dump my brain on some po
On Tue, 21 Aug 2012 18:06:38 +0200
Andres Freund wrote:
> On Tuesday, August 21, 2012 05:56:58 PM Robert Haas wrote:
> > On Tue, Aug 21, 2012 at 11:31 AM, Andres Freund
> >
> wrote:
> > > On Tuesday, August 21, 2012 05:30:28 PM Robert Haas wrote:
> > >> On Thu, Aug 16, 2012 at 10:53 PM, David G
Robert Haas writes:
> On Tue, Aug 21, 2012 at 10:47 AM, Tom Lane wrote:
>> * Checkpointer process split broke fsync'ing
>> ** bug is fixed, but now we had better recheck earlier performance claims
>>
>> Is anyone actually going to do any performance testing on this?
> I am unlikely to have time
On Mon, Aug 20, 2012 at 5:54 PM, Greg Sabino Mullane wrote:
>> 3) use a purposefully slow hashing function like bcrypt.
>>
>> but I disagree: I don't like any scheme that encourages use of low
>> entropy passwords.
>
> Perhaps off-topic, but how to do you figure that?
Yeah -- bcrypt's main claim
Tom,
* Tom Lane (t...@sss.pgh.pa.us) wrote:
> Um, I don't believe we do any case-insensitive search now, do we?
No, I don't suppose we do.. I was thinking we ran quote_ident() on the
search-string side, but apparently we don't, meaning:
select * from TE
doesn't find 'test'. I suppose it's alr
On Tue, Aug 21, 2012 at 2:14 PM, Tom Lane wrote:
> Robert Haas writes:
>> On Tue, Aug 21, 2012 at 12:13 PM, Tom Lane wrote:
>>> I can work on it if you're still swamped. I think it is probably
>>> fixable by treating the view options as attached to the _RETURN rule
>>> instead of the base table
On Tue, Aug 21, 2012 at 1:52 PM, Tom Lane wrote:
> In short, I think we might be able to make this fast, and more usable,
> just with hacking on psql's query generation rules. There's no need for
> server-side changes.
So, I think that hacking on psql's query generation rules may well be
a good
Robert Haas writes:
> So, I think that hacking on psql's query generation rules may well be
> a good idea, but shouldn't we also be bumping procost for the
> pg_whatever_is_visible functions? I mean, Stephen's information
> suggests that those values are pretty clearly wrong, regardless of
> anyt
Robert Haas writes:
> On Tue, Aug 21, 2012 at 2:14 PM, Tom Lane wrote:
>> Yeah, that sounds about right. You want to do it, or shall I?
> If you don't mind dealing with it, that's great. If you'd prefer that
> I cleaned up my own mess, I'll take care of it.
I can do it. I have nothing on my
Robert Haas writes:
> On Tue, Aug 21, 2012 at 12:13 PM, Tom Lane wrote:
>> I can work on it if you're still swamped. I think it is probably
>> fixable by treating the view options as attached to the _RETURN rule
>> instead of the base table in pg_dump's objects. (There is an ALTER VIEW
>> comma
> No. I get the same backtrace when I try against the 9.1.5 (REL9_1_STABLE)
> branch.
OK, not a regression then.
Can you install plpython3u using non-Activestate python?
--
Josh Berkus
PostgreSQL Experts Inc.
http://pgexperts.com
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgre
On Tue, Aug 21, 2012 at 10:37 PM, Josh Berkus wrote:
> On 8/21/12 6:34 AM, Sachin Srivastava wrote:
> > Hi all,
> >
> > On my Mac 10.6.8 using ActiveState Python 3.2.2, I am getting a crash
> when
> > I try to execute "CREATE EXTENSION plpython3u"
> > This is the backtrace:
>
> Does it work in Po
On Tue, Aug 21, 2012 at 12:13 PM, Tom Lane wrote:
> Robert Haas writes:
>> On Tue, Aug 21, 2012 at 10:47 AM, Tom Lane wrote:
>>> * View options are problematic for pg_dump
>>>
>>> I had hoped those who created this problem were going to fix it, but
>>> given the lack of response I guess I'll hav
Tom Lane wrote:
> We'd still emit quote_ident output, which means that if you did
>
> select * from TE
>
> it would change that to
>
> select * from "TEST
>
> (assuming you had say TEST1 and TEST2 so it couldn't complete
> further).
> if the word-so-far has a leading quote and
Stephen Frost writes:
> That's the kind of concern that I was expecting, to be honest. :) As
> Kevin's pointed out, it's not likely to be needed anyway.. There's a
> bit of an open question still regarding case-insensitive searching, but
> perhaps we let that be slow and only done if we don't ge
Stephen Frost writes:
> There's a couple of other interesting corner cases, such as:
Yeah. I had been thinking of this as purely a performance issue, but
if we want to consider adjusting the visible behavior as well, that
makes it a completely different thing.
> select * from "spa
> Will return
From: Tom Lane [t...@sss.pgh.pa.us]
Sent: Tuesday, August 21, 2012 10:31 PM
Amit Kapila writes:
> [mailto:pgsql-hackers-ow...@postgresql.org] On Behalf Of Tom Lane
>>> * pg_ctl crashes on Win32 when neither PGDATA nor -D specified
>>> I'm not sure that this qualifies as a release blocker either -
* Tom Lane (t...@sss.pgh.pa.us) wrote:
> The LIKE idea is interesting. What you'd still need is to suppress the
> quote_ident function call so that it becomes just "relname LIKE 'foo%'".
> Which seems do-able if possibly rather ugly. That would leave us with
> SELECT ... FROM foo being fast but S
Stephen Frost writes:
> * Robert Haas (robertmh...@gmail.com) wrote:
>> Is this a regression versus earlier releases, or just a bad thing in general?
> Alright, so, yea, the commit I was referring to is this one:
> e84487f67a0d216f3db87b2558f1edd322a09e48
> Which was apparently in the 8.3 dev cyc
* Tom Lane (t...@sss.pgh.pa.us) wrote:
> Um ... I don't see any difference in the clause ordering from 8.2
> forward. "SELECT * FROM baz" produces a query like this in 8.2:
Odd.. I could have sworn I saw a difference in the query generated,
but perhaps I just assumed it was reordered, since it e
* Kevin Grittner (kevin.gritt...@wicourts.gov) wrote:
> That already seems to work for me.
Ah, yes, that does.. I was using the query from tab-complete.c, which
wraps it in quote_ident(c.relanme), which ends up preventing us from
using the index.
There's a couple of other interesting corner case
Stephen Frost writes:
> * Stephen Frost (sfr...@snowman.net) wrote:
>>> Is this a regression versus earlier releases, or just a bad thing in
>>> general?
>> It's really a regression- in prior releases
> Sorry, to clarify (after reading through my -hackers inbox a bit more
> and realizing you we
On 8/21/12 6:34 AM, Sachin Srivastava wrote:
> Hi all,
>
> On my Mac 10.6.8 using ActiveState Python 3.2.2, I am getting a crash when
> I try to execute "CREATE EXTENSION plpython3u"
> This is the backtrace:
Does it work in Postgres 9.1?
--
Josh Berkus
PostgreSQL Experts Inc.
http://pgexperts.
Stephen Frost wrote:
> Would people accept adding an index on pg_class.relname to support
> fast tab-completion? Or is this going to expand into figuring out
> how to support index-based partial lookups for the 'name' type, so
> we could use the existing index (if that's even possible
> to do..
Amit Kapila writes:
> [mailto:pgsql-hackers-ow...@postgresql.org] On Behalf Of Tom Lane
>> * pg_ctl crashes on Win32 when neither PGDATA nor -D specified
>> I'm not sure that this qualifies as a release blocker either --- isn't
>> it a plain-vanilla pre-existing bug?
> This is to handle one part
Alvaro Herrera writes:
> Excerpts from Tom Lane's message of mar ago 21 10:47:41 -0400 2012:
>> * pg_ctl crashes on Win32 when neither PGDATA nor -D specified
>>
>> I'm not sure that this qualifies as a release blocker either --- isn't
>> it a plain-vanilla pre-existing bug? And what does the pr
* Robert Haas (robertmh...@gmail.com) wrote:
> On Thu, Aug 16, 2012 at 10:37 PM, Stephen Frost wrote:
> > When doing tab-completion under 9.1, pg_table_is_visible(oid) is slow
> > and is ending up as the first thing tested against all the rows
> > in pg_class. Increasing the cost of pg_tabl
Hi,
I am reviewing this one year old change again before backporting it to 9.1.3 for
production use.
ATM, I believe the code is correct, but I don't want to miss the change to spot
possible errors, so please let me dump my brain on some points:
- IIUC, SIGetDataEntries() can return 0 when i
Robert Haas writes:
> On Tue, Aug 21, 2012 at 10:47 AM, Tom Lane wrote:
>> * View options are problematic for pg_dump
>>
>> I had hoped those who created this problem were going to fix it, but
>> given the lack of response I guess I'll have to.
> This is my fault, but my hackers inbox got flood
On Tue, Aug 21, 2012 at 06:04:42PM +0900, Tatsuo Ishii wrote:
> Hi,
>
> I am thinking about to implement "multi-master" option for pgbench.
> Supose we have multiple PostgreSQL running on host1 and host2.
> Something like "pgbench -c 10 -h host1,host2..." will create 5
> connections to host1 and h
On Tuesday, August 21, 2012 05:56:58 PM Robert Haas wrote:
> On Tue, Aug 21, 2012 at 11:31 AM, Andres Freund
wrote:
> > On Tuesday, August 21, 2012 05:30:28 PM Robert Haas wrote:
> >> On Thu, Aug 16, 2012 at 10:53 PM, David Gould wrote:
> >> > A warning, on RHEL 6.1 (2.6.32-131.4.1.el6.x86_64 #1
On Wed, Aug 15, 2012 at 8:43 PM, Bruce Momjian wrote:
> Are there any TODO items here?
It's possible there's something we want to change here, but it's far
from obvious what that thing is. Our WAL file handling is
ridiculously hard to understand, but the problem with changing it is
that there wi
Hi.
The latest document (doc/src/sgml/ddl.sgml) says
===
2974
2975
2976
2977 Constraint exclusion only works when the query's WHERE
2978 clause contains constants. A parameterized query will not be
2979 optimized, since the plan
On Tue, Aug 21, 2012 at 11:31 AM, Andres Freund wrote:
> On Tuesday, August 21, 2012 05:30:28 PM Robert Haas wrote:
>> On Thu, Aug 16, 2012 at 10:53 PM, David Gould wrote:
>> > A warning, on RHEL 6.1 (2.6.32-131.4.1.el6.x86_64 #1 SMP) we have had
>> > horrible problems caused by transparent_hugep
On Wed, Aug 15, 2012 at 6:23 PM, Bruce Momjian wrote:
> Has this been addressed? A TODO?
I don't think anything's been done about it. According to your email
of October 11, 2011, you already did add a TODO for this.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise Postg
* Stephen Frost (sfr...@snowman.net) wrote:
> > Is this a regression versus earlier releases, or just a bad thing in
> > general?
>
> It's really a regression- in prior releases
Sorry, to clarify (after reading through my -hackers inbox a bit more
and realizing you were probably asking about 9.2
On Tue, Aug 14, 2012 at 5:41 PM, Bruce Momjian wrote:
> Did these comment updates ever get addressed?
Partially.
I just made a commit to clean up the rest of it.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
--
Sent via pgsql-hackers mailing list
Robert,
* Robert Haas (robertmh...@gmail.com) wrote:
> On Thu, Aug 16, 2012 at 10:37 PM, Stephen Frost wrote:
> > When doing tab-completion under 9.1, pg_table_is_visible(oid) is slow
> > and is ending up as the first thing tested against all the rows
> > in pg_class. Increasing the cost o
On Sat, Aug 11, 2012 at 6:11 PM, Jeff Janes wrote:
> However, I do think we will want to add a way to query for the time of
> the last reset, as other monitoring features are going that way.
That should be easy to add.
> Is it OK that the count is reset upon a server restart?
I think it's OK.
On Tuesday, August 21, 2012 05:30:28 PM Robert Haas wrote:
> On Thu, Aug 16, 2012 at 10:53 PM, David Gould wrote:
> > A warning, on RHEL 6.1 (2.6.32-131.4.1.el6.x86_64 #1 SMP) we have had
> > horrible problems caused by transparent_hugepages running postgres on
> > largish systems (128GB to 512GB
From: pgsql-hackers-ow...@postgresql.org
[mailto:pgsql-hackers-ow...@postgresql.org] On Behalf Of Tom Lane
> * pg_ctl crashes on Win32 when neither PGDATA nor -D specified
> I'm not sure that this qualifies as a release blocker either --- isn't
> it a plain-vanilla pre-existing bug? And what does
On Thu, Aug 16, 2012 at 10:53 PM, David Gould wrote:
> A warning, on RHEL 6.1 (2.6.32-131.4.1.el6.x86_64 #1 SMP) we have had
> horrible problems caused by transparent_hugepages running postgres on
> largish systems (128GB to 512GB memory, 32 cores). The system sometimes
> goes 99% system time and
On Thu, Aug 16, 2012 at 10:37 PM, Stephen Frost wrote:
> Greetings,
>
> When doing tab-completion under 9.1, pg_table_is_visible(oid) is slow
> and is ending up as the first thing tested against all the rows
> in pg_class. Increasing the cost of pg_table_is_visible() up to
> 10 causes it
On Tue, Aug 21, 2012 at 10:47 AM, Tom Lane wrote:
> ... or at least, that's what the schedule says. I don't think we can
> honestly produce a "release candidate" when there are still open issues
> listed as blockers at
> http://wiki.postgresql.org/wiki/PostgreSQL_9.2_Open_Items
> We need to eithe
>> I am thinking about to implement "multi-master" option for pgbench.
>> Supose we have multiple PostgreSQL running on host1 and host2.
>> Something like "pgbench -c 10 -h host1,host2..." will create 5
>> connections to host1 and host2 and send queries to host1 and host2.
>> The point of this func
Excerpts from Tom Lane's message of mar ago 21 10:47:41 -0400 2012:
> * pg_ctl crashes on Win32 when neither PGDATA nor -D specified
>
> I'm not sure that this qualifies as a release blocker either --- isn't
> it a plain-vanilla pre-existing bug? And what does the proposed patch
> have to do wit
On Mon, Aug 20, 2012 at 4:45 AM, Craig Ringer wrote:
> Trying again with the attachments; the archiver only seemed to see the first
> patch despite all three being attached. Including patches inline; if you
> want 'em prettier, see:
>
> https://github.com/ringerc/postgres/tree/sequence_documenta
On Mon, Aug 20, 2012 at 09:33:45PM -0700, Jeff Davis wrote:
> On Mon, 2012-08-20 at 19:17 -0400, David Johnston wrote:
> > Ideally the decision of whether to do so could be a client
> > decision. Not storing intra-transaction changes is easier than
> > storing all changes. At worse you could stag
> Please add your patch here:
>
> https://commitfest.postgresql.org/action/commitfest_view/open
>
> --
> Robert Haas
> EnterpriseDB: http://www.enterprisedb.com
> The Enterprise PostgreSQL Company
Hi, Robert
I added it under "Miscellaneous".
https://commitfest.postgresql.org/action/patc
... or at least, that's what the schedule says. I don't think we can
honestly produce a "release candidate" when there are still open issues
listed as blockers at
http://wiki.postgresql.org/wiki/PostgreSQL_9.2_Open_Items
We need to either get something done about those, conclude that they're
not b
On Mon, Aug 20, 2012 at 9:52 PM, Qi Huang wrote:
> Hi, hackers
> I made the final version tablesample patch. It is implementing SYSTEM
> and BERNOULLI sample method, which is basically "feature-complete". The
> regression test is also included in this patch.
> There is an wiki documentati
On Mon, Aug 20, 2012 at 5:14 PM, Jeff Davis wrote:
> On Mon, 2012-08-20 at 16:50 -0400, Robert Haas wrote:
>> #3 for foreign tables.
>
> I'm skeptical of that approach for two reasons:
>
> (1) It will be hard to inform users which constraints are enforced and
> which aren't.
The thing to keep in
Hi,
new version with a lot more cleanup is attached.
2012-07-22 22:03 keltezéssel, Boszormenyi Zoltan írta:
Attached is the revised (and a lot leaner, more generic) lock timeout patch,
which introduces new functionality for the timeout registration framework.
The new functionality is called "ex
Jeff Davis wrote:
> On Mon, 2012-08-20 at 19:32 -0500, Kevin Grittner wrote:
>> Josh Berkus wrote:
>>
>>> This is sounding like a completely runaway spec on what should
>>> be a simple feature.
>>
>> I hate to contribute to scope creep (or in this case scope
>> screaming down the tracks at fu
Tatsuo Ishii writes:
> I am thinking about to implement "multi-master" option for pgbench.
> Supose we have multiple PostgreSQL running on host1 and host2.
> Something like "pgbench -c 10 -h host1,host2..." will create 5
> connections to host1 and host2 and send queries to host1 and host2.
> The p
On Mon, Aug 20, 2012 at 6:44 PM, Tom Lane wrote:
> Robert Haas writes:
>> On Mon, Aug 20, 2012 at 4:27 PM, Tom Lane wrote:
>>> Surely we could just prevent creation of the FSM until the table has
>>> reached at least, say, 10 blocks.
>>>
>>> Any threshold beyond one block would mean potential sp
Hi all,
On my Mac 10.6.8 using ActiveState Python 3.2.2, I am getting a crash when
I try to execute "CREATE EXTENSION plpython3u"
This is the backtrace:
Program received signal SIGABRT, Aborted.
0x7fff899a40b6 in __kill ()
(gdb) bt
#0 0x7fff899a40b6 in __kill ()
#1 0x7fff89a449f6 in
On 20.08.2012 00:31, Alexander Korotkov wrote:
On Thu, Aug 16, 2012 at 4:40 PM, Heikki Linnakangas<
heikki.linnakan...@enterprisedb.com> wrote:
On 15.08.2012 11:34, Alexander Korotkov wrote:
Ok, we've to decide if we need "standard" histogram. In some cases it can
be used for more accurate e
On Tue, Aug 21, 2012 at 6:04 PM, Tatsuo Ishii wrote:
> Hi,
>
> I am thinking about to implement "multi-master" option for pgbench.
> Supose we have multiple PostgreSQL running on host1 and host2.
> Something like "pgbench -c 10 -h host1,host2..." will create 5
> connections to host1 and host2 and
I have written one approach to audit tables, available from
https://github.com/akaariai/pgsql_shadow_tables
The approach is that every table is backed by a similar audit table +
some meta information. The tables and triggers to update the audit
tables are managed by plpgsql procedures.
While
Hi,
I am thinking about to implement "multi-master" option for pgbench.
Supose we have multiple PostgreSQL running on host1 and host2.
Something like "pgbench -c 10 -h host1,host2..." will create 5
connections to host1 and host2 and send queries to host1 and host2.
The point of this functionality
On 08/21/2012 01:52 PM, Jeff Davis wrote:
On Mon, 2012-08-20 at 16:32 -0700, Josh Berkus wrote:
Personally, I would prefer a tool which just made it simpler to build my
own triggers, and made it automatic for the history table to track
changes in the live table. I think anything we build which
On 2012-08-20 18:36, Tom Lane wrote:
Alvaro Herrera writes:
Excerpts from Alex Hunsaker's message of lun ago 20 12:03:11 -0400 2012:
Hrm seems to work for me. What version of perl is this?
$ perl -V
Summary of my perl5 (revision 5 version 16 subversion 0) configuration:
I can reproduce the fa
90 matches
Mail list logo
