After some significant prior discussion:
Here is what I've found:
Doing the simple thing is extremely wasteful. Let's take TSRANGE, for
instance:
4 bytes type oid
1 flag byte
8 bytes lower bound
8 bytes upper bound
But when constructing the value itself, it starts off with VARHDRSZ
On Wed, Feb 9, 2011 at 07:22, Fujii Masao masao.fu...@gmail.com wrote:
On Wed, Feb 9, 2011 at 2:02 PM, Simon Riggs si...@2ndquadrant.com wrote:
Why did you change the default to on? This would surprise people who are
used to PITR.
You pointed out that the code did not match the documented
Updated patch.
Changes:
* Addressed Erik's review comments.
* Fixed issue with range @ elem found by Erik.
* Merged with latest HEAD
* Changed representation to be more efficient and more robust
(could use some testing though, because I just did this tonight)
TODO:
* send/recv --
Attached is an updated 64-bit pgbench patch that works as expected for
all of the most common pgbench operations, including support for scales
above the previous boundary of just over 21,000. Here's the patched
version running against a 303GB database with a previously unavailable
scale
On Tue, 2011-02-08 at 15:10 -0500, Chris Browne wrote:
It's more than a bit sad... The RangeType change has the massive merit
of enabling some substantial development changes, where we can get rid
of whole classes of comparison clauses, and hopefully whole classes of
range errors. That was
On 09/02/11 04:52, Hitoshi Harada wrote:
2010/12/31 Jan Urbański wulc...@wulczer.org:
(continuing the flurry of patches)
Here's a patch that stops PL/Python from removing the function's
arguments from its globals dict after calling it. It's
an incremental patch on top of the
On 27/01/11 22:42, Jan Urbański wrote:
On 23/12/10 14:50, Jan Urbański wrote:
Here's a patch implementing properly invalidating functions that have
composite type arguments after the type changes, as mentioned in
http://archives.postgresql.org/pgsql-hackers/2010-12/msg01991.php. It's
an
On 06/02/11 20:12, Jan Urbański wrote:
On 27/01/11 22:58, Jan Urbański wrote:
On 23/12/10 14:56, Jan Urbański wrote:
Here's a patch implementing traceback support for PL/Python mentioned in
http://archives.postgresql.org/pgsql-hackers/2010-12/msg01991.php. It's
an incremental patch on top of
On Sun, Feb 6, 2011 at 23:06, Brar Piening b...@gmx.de wrote:
On Sun, 30 Jan 2011 21:26:22 +0100, Magnus Hagander mag...@hagander.net
wrote:
it's not something we should hold up the CF / release for.
I agree.
At least it should get some more testing besides mine.
I've set up virtual
Tom Lane t...@sss.pgh.pa.us writes:
Like ALTER THING SET SCHEMA, ALTER THING SET EXTENSION is implicitly
assuming that there can be only one owning extension for an object.
Yes, I worked from the SET SCHEMA variant and mentally mapped SET
EXTENSION there, if looked like the same idea applied to
On 9 February 2011 02:11, Robert Haas robertmh...@gmail.com wrote:
On Tue, Feb 8, 2011 at 8:30 PM, Andrew Dunstan and...@dunslane.net wrote:
Quite right, but the commitfest manager isn't meant to be a substitute for
one. Bug fixes aren't subject to the same restrictions of feature changes.
On Thu, Feb 3, 2011 at 11:19, Magnus Hagander mag...@hagander.net wrote:
On Wed, Feb 2, 2011 at 18:00, Magnus Hagander mag...@hagander.net wrote:
On Wed, Feb 2, 2011 at 17:43, Heikki Linnakangas
heikki.linnakan...@enterprisedb.com wrote:
On 02.02.2011 16:36, Magnus Hagander wrote:
When
Hi!
I've changed the format of the URLs in the git commit messages so they
no longer contain a semicolon, since a number of people reported that
made them stop working for users of gmail (which is a fair amount of
users..) They'll now go to /pg/commitdiff/hash instead which will
redirect back to
2011/2/9 Magnus Hagander mag...@hagander.net:
Hi!
I've changed the format of the URLs in the git commit messages so they
no longer contain a semicolon, since a number of people reported that
made them stop working for users of gmail (which is a fair amount of
users..) They'll now go to
On 09.02.2011 00:04, Kevin Grittner wrote:
(1) When HTABs are created, there is the max_size, which is what
the PredicateLockShmemSize function must use in its calculations,
and the init_size, which is what will initially be allocated (and
so, is probably what you see in the usage at the end of
On Wed, Feb 9, 2011 at 3:53 AM, Robert Haas robertmh...@gmail.com wrote:
That having been said, there is at least one part of this patch which
looks to be in pretty good shape and seems independently useful
regardless of what happens to the rest of it, and that is the code
that sends replies
Hi,
I have create the following tables:
1. rnc table
CREATE TABLE act_rnc(rnc_id integer NOT NULL PRIMARY KEY, rnc_data BYTEA);
2. rncgen table
CREATE TABLE act_rncgen(rnc_id integer NOT NULL PRIMARY KEY, rncsubObj_Cnt
integer, rncgen_data BYTEA);
3. iuo table which has a foreign key reference
On 09.02.2011 12:15, Sander, Ingo (NSN - DE/Munich) wrote:
Hi,
I have create the following tables:
1. rnc table
CREATE TABLE act_rnc(rnc_id integer NOT NULL PRIMARY KEY, rnc_data BYTEA);
2. rncgen table
CREATE TABLE act_rncgen(rnc_id integer NOT NULL PRIMARY KEY, rncsubObj_Cnt
integer,
On Thu, Feb 3, 2011 at 00:24, Marko Tiikkaja
marko.tiikk...@cs.helsinki.fi wrote:
.. and here's the patch. I'm not too confident with the code I added to
storage/lmgr/lock.c, but it seems to be working.
Sorry for the delayed review.
The patch needs adjustment of OIDs for recently commits, but
Hello,
I am a computer student in belgium, for my academic project I am working to
an extension of postgresql 9 under win xp, by creating h DLL in Visual C++
2008 - I am new in both environments; To start and understand how does it
works, I tried to compile the example complex.c which is in the
On Tue, 8 Feb 2011 08:49:36 -0500
Robert Haas robertmh...@gmail.com wrote:
On Tue, Feb 8, 2011 at 4:42 AM, Shigeru HANADA
han...@metrosystems.co.jp wrote:
I'll submit revised file_fdw patch after removing IsForeignTable()
catalog lookup along Heikki's proposal.
So I'm a bit confused. I
On mån, 2011-02-07 at 12:55 -0500, Robert Haas wrote:
On Mon, Feb 7, 2011 at 12:43 PM, Tom Lane t...@sss.pgh.pa.us wrote:
Robert Haas robertmh...@gmail.com writes:
... Well, the current CommitFest ends in one week, ...
Really? I thought the idea for the last CF of a development cycle was
On 02/09/2011 07:53 AM, Peter Eisentraut wrote:
On mån, 2011-02-07 at 12:55 -0500, Robert Haas wrote:
On Mon, Feb 7, 2011 at 12:43 PM, Tom Lanet...@sss.pgh.pa.us wrote:
Robert Haasrobertmh...@gmail.com writes:
... Well, the current CommitFest ends in one week, ...
Really? I thought the
Andrew Dunstan and...@dunslane.net writes:
On 02/09/2011 07:53 AM, Peter Eisentraut wrote:
The previous three commit fests contained about 50 patches each and
lasted one month each. The current commit fest contains about 100
patches, so it shouldn't be surprising that it will take about 2
Dimitri Fontaine dimi...@2ndquadrant.fr writes:
As far as upgrade script for contrib extensions are concerned, we will
be able to produce them from SQL, right?
Hm, interesting idea, but I'm afraid that pg_describe_object doesn't
produce exactly the syntax you need.
I had personally been
Tom Lane t...@sss.pgh.pa.us writes:
Hm, interesting idea, but I'm afraid that pg_describe_object doesn't
produce exactly the syntax you need.
It's very close. I've produced the previous set like that and the only
problem I had were with operator class and family objects, and with
array types.
On Tue, Feb 08, 2011 at 09:09:48PM -0500, Robert Haas wrote:
If we don't allocate all the memory up front, does that allow memory
to be dynamically shared between different hash tables in shared
memory? I'm thinking not, but...
Frankly, I think this is an example of how our current shared
Heikki Linnakangas heikki.linnakan...@enterprisedb.com wrote:
(2) The predicate lock and lock target initialization code was
initially copied and modified from the code for heavyweight
locks. The heavyweight lock code adds 10% to the calculated
maximum size. So I wound up doing that for
On Feb 9, 2011, at 3:44 AM, Alex Hunsaker wrote:
So the merge while not exactly trivial was fairly simple. However it
would be great if you could give it another look over.
Find attached v7 changes include:
- rebased against HEAD
- fix potential use of uninitialized dims[cur_depth]
-
On 02/09/2011 04:16 PM, David Fetter wrote:
On Tue, Feb 08, 2011 at 09:09:48PM -0500, Robert Haas wrote:
Frankly, I think this is an example of how our current shared memory
model is a piece of garbage.
What other model(s) might work better?
Thread based, dynamically allocatable and
Dan Ports d...@csail.mit.edu wrote:
I think for SerializableXidHash we should probably just initially
allocate it at its maximum size. Then it'll match the PredXact
list which is allocated in full upfront, and there's no risk of
being able to allocate a transaction but not register its xid.
On Wed, Feb 09, 2011 at 01:17:06PM +, Bruce Momjian wrote:
Remove more SGML tabs.
Perhaps we should see about putting something in .git/hooks/pre-commit
so people can focus on more substantive matters.
Is there some kind of cross-platform way to do this? I'm thinking
that given the fact
On Wed, Feb 9, 2011 at 9:42 AM, Tom Lane t...@sss.pgh.pa.us wrote:
Andrew Dunstan and...@dunslane.net writes:
On 02/09/2011 07:53 AM, Peter Eisentraut wrote:
The previous three commit fests contained about 50 patches each and
lasted one month each. The current commit fest contains about 100
michel wildcat m.wildca...@gmail.com wrote:
I am a computer student in belgium, for my academic project I am
working to an extension of postgresql 9 under win xp, by creating
h DLL in Visual C++ 2008 - I am new in both environments; To start
and understand how does it works, I tried to
On Feb 9, 2011 5:01 PM, David Fetter da...@fetter.org wrote:
On Wed, Feb 09, 2011 at 01:17:06PM +, Bruce Momjian wrote:
Remove more SGML tabs.
Perhaps we should see about putting something in .git/hooks/pre-commit
so people can focus on more substantive matters.
Is there some kind of
On tis, 2011-02-08 at 22:17 +, Thom Brown wrote:
postgres=# create table meow (id serial, stuff text collate de_XX);
NOTICE: CREATE TABLE will create implicit sequence meow_id_seq for
serial column meow.id
ERROR: collation de_XX for current database encoding UTF8 does not exist
LINE 1:
On Wed, Feb 9, 2011 at 7:53 AM, Peter Eisentraut pete...@gmx.net wrote:
Moreover, under the current process, it is apparent that reviewing is
the bottleneck. More code gets written than gets reviewed. By
insisting on the current schedule, we would just push the growing review
backlog ahead
On Wed, Feb 9, 2011 at 10:38 AM, Markus Wanner mar...@bluegap.ch wrote:
On 02/09/2011 04:16 PM, David Fetter wrote:
On Tue, Feb 08, 2011 at 09:09:48PM -0500, Robert Haas wrote:
Frankly, I think this is an example of how our current shared memory
model is a piece of garbage.
What other
On Wed, Feb 9, 2011 at 7:38 AM, Shigeru HANADA
han...@metrosystems.co.jp wrote:
On Tue, 8 Feb 2011 08:49:36 -0500
Robert Haas robertmh...@gmail.com wrote:
On Tue, Feb 8, 2011 at 4:42 AM, Shigeru HANADA
han...@metrosystems.co.jp wrote:
I'll submit revised file_fdw patch after removing
On Wed, Feb 9, 2011 at 7:12 AM, Itagaki Takahiro
itagaki.takah...@gmail.com wrote:
One issue might be in pg_locks, as you pointed out in the previous mail:
if a session holds both a transaction level and a session level lock
on the same resource, only one of them will appear in pg_locks.
Also,
On 02/09/2011 12:26 PM, Robert Haas wrote:
On Wed, Feb 9, 2011 at 7:38 AM, Shigeru HANADA
han...@metrosystems.co.jp wrote:
On Tue, 8 Feb 2011 08:49:36 -0500
Robert Haasrobertmh...@gmail.com wrote:
On Tue, Feb 8, 2011 at 4:42 AM, Shigeru HANADA
han...@metrosystems.co.jp wrote:
I'll submit
On Feb 9, 2011, at 9:20 AM, Robert Haas wrote:
There are certainly some patches in this CommitFest that need more
attention than that, and that probably need the attention of a senior
community member. Jeff's range types patch and Alvaro's key lock
patch are two of those. And I would be
On Feb 8, 2011, at 6:48 PM, Tom Lane wrote:
Like ALTER THING SET SCHEMA, ALTER THING SET EXTENSION is implicitly
assuming that there can be only one owning extension for an object.
Furthermore, it's not really intended for *removal* of an object from an
extension (a concept that doesn't even
On Wed, Feb 9, 2011 at 1:09 PM, David E. Wheeler da...@kineticode.com wrote:
Frankly, I think you should surrender some of those 14 and cajole some other
folks to take on more.
Happily... only trouble is, I suck at cajoling. Even my begging is
distinctly sub-par.
Plase?
--
Robert
On Wed, Feb 9, 2011 at 12:45 PM, Andrew Dunstan and...@dunslane.net wrote:
Itagaki-san published a patch for this about about 12 hours ago in the
file_fdw thread that looks pretty committable to me.
OK, excellent.
This whole API thing is a breakout from file_fdw, because the original
The lastest clang svn tip (2.9-to-be, I guess) builds PostgreSQL out of
the box and most tests pass. Specifically, it no longer chokes on
-D_GNU_SOURCE on Linux, which was the previously reported blocker.
Warnings:
Lots of these:
clang: warning: argument unused during compilation: '-mthreads'
On Feb 9, 2011, at 10:29 AM, Robert Haas wrote:
Frankly, I think you should surrender some of those 14 and cajole some other
folks to take on more.
Happily... only trouble is, I suck at cajoling. Even my begging is
distinctly sub-par.
Plase?
Try this:
“Listen up, bitches!
* Robert Haas (robertmh...@gmail.com) wrote:
On Wed, Feb 9, 2011 at 1:09 PM, David E. Wheeler da...@kineticode.com wrote:
Frankly, I think you should surrender some of those 14 and cajole some
other folks to take on more.
Happily... only trouble is, I suck at cajoling. Even my begging
On Wed, Feb 9, 2011 at 1:35 PM, Stephen Frost sfr...@snowman.net wrote:
* Robert Haas (robertmh...@gmail.com) wrote:
On Wed, Feb 9, 2011 at 1:09 PM, David E. Wheeler da...@kineticode.com
wrote:
Frankly, I think you should surrender some of those 14 and cajole some
other folks to take on
On Wed, Feb 9, 2011 at 5:05 AM, Magnus Hagander mag...@hagander.net wrote:
Hi!
I've changed the format of the URLs in the git commit messages so they
no longer contain a semicolon, since a number of people reported that
made them stop working for users of gmail (which is a fair amount of
On Wed, Feb 9, 2011 at 1:32 PM, David E. Wheeler da...@kineticode.com wrote:
On Feb 9, 2011, at 10:29 AM, Robert Haas wrote:
Frankly, I think you should surrender some of those 14 and cajole some
other folks to take on more.
Happily... only trouble is, I suck at cajoling. Even my begging
On Feb 9, 2011, at 10:56 AM, Robert Haas wrote:
“Listen up, bitches! I'm tired of Tom and me having to do all the work. All
of you who submitted patches need to review some other patches! If you
haven't submitted a review for someone else's patch by commitfest end, your
patches will be
* Robert Haas (robertmh...@gmail.com) wrote:
Of the fourteen I signed up for, 10 are now marked Committed or
Returned with Feedback. Of the remaining four, there are two that
could use more eyes:
MULTISET functions
I'll work on this one.
Change pg_last_xlog_receive_location not to move
On Tue, Feb 08, 2011 at 09:40:38AM -0500, Andrew Dunstan wrote:
On 02/03/2011 01:20 PM, Andrew Dunstan wrote:
Well, the question seems to be whether or not it's a reasonable
price to pay. On the whole I'm inclined to think it is, especially
when it can be avoided by updating your code, which
On Feb 9, 2011, at 12:25 PM, Robert Haas wrote:
On Wed, Feb 9, 2011 at 10:38 AM, Markus Wanner mar...@bluegap.ch wrote:
On 02/09/2011 04:16 PM, David Fetter wrote:
On Tue, Feb 08, 2011 at 09:09:48PM -0500, Robert Haas wrote:
Frankly, I think this is an example of how our current shared
On Wed, Feb 9, 2011 at 08:24, Alexey Klyukin al...@commandprompt.com wrote:
What was actually broken in encode_array_literal support of composite types
(it converted perl hashes to the literal composite-type constants, expanding
nested arrays along the way) ? I think it would be a useful
--On 9. Februar 2011 13:45:11 -0500 Robert Haas robertmh...@gmail.com
wrote:
Of the fourteen I signed up for, 10 are now marked Committed or
Returned with Feedback. Of the remaining four, there are two that
could use more eyes:
I'd happily jump in and look into one of those, but before
On Wed, Feb 9, 2011 at 2:01 PM, David E. Wheeler da...@kineticode.com wrote:
ha ha! Alas, I'm completely overcommitted at this point. Been having a hard
time making time for PGXN. I've been tracking the extension stuff closely,
though, as you can imagine.
It's a common problem, and of course
On Wed, Feb 9, 2011 at 2:16 PM, A.M. age...@themactionfaction.com wrote:
On Feb 9, 2011, at 12:25 PM, Robert Haas wrote:
On Wed, Feb 9, 2011 at 10:38 AM, Markus Wanner mar...@bluegap.ch wrote:
On 02/09/2011 04:16 PM, David Fetter wrote:
On Tue, Feb 08, 2011 at 09:09:48PM -0500, Robert Haas
Greg,
* Greg Smith (g...@2ndquadrant.com) wrote:
I took that complexity out and just put a hard line
in there instead: if scale=2, you get bigints. That's not
very different from the real limit, and it made documenting when the
switch happens easy to write and to remember.
Agreed
On 02/09/2011 06:25 PM, Robert Haas wrote:
On Wed, Feb 9, 2011 at 10:38 AM, Markus Wanner mar...@bluegap.ch wrote:
Thread based, dynamically allocatable and resizeable shared memory, as
most other projects and developers use, for example.
I didn't mean to say we should switch to that model.
On Wed, Feb 9, 2011 at 2:51 PM, Markus Wanner mar...@bluegap.ch wrote:
On 02/09/2011 06:25 PM, Robert Haas wrote:
On Wed, Feb 9, 2011 at 10:38 AM, Markus Wanner mar...@bluegap.ch wrote:
Thread based, dynamically allocatable and resizeable shared memory, as
most other projects and developers
We are making some performance measurements, we are trying to determine query
execution behavior. Lets say we have 4 tables T1, T2, T3 and T4
and the query has the form:
select * from T1, T2, T3, T4 where (T1.a = T2.b and T2.c = T3.d
T3.e = T4.f)
where a,b,c,d,e,f are properties of the
pg...@j-davis.com (Jeff Davis) writes:
On Tue, 2011-02-08 at 15:10 -0500, Chris Browne wrote:
It's more than a bit sad... The RangeType change has the massive merit
of enabling some substantial development changes, where we can get rid
of whole classes of comparison clauses, and hopefully
One of the things I'd particularly like to use range types for is to
make it easier to construct range-related queries. Classic example is
that of reports that work on date ranges.
I create a table that will have transaction data:
CREATE TABLE some_data (
id serial,
whensit date
--
On tis, 2011-02-08 at 00:32 -0500, Steve Singer wrote:
On 11-02-06 11:40 AM, Jan Urbański wrote:
PFA an updated patch with documentation.
Yeah, changed them.
Those changes look fine. The tests now pass.
I've attached a new version of the patch that fixes a few typos/wording
On Wed, 2011-02-09 at 16:20 -0500, Chris Browne wrote:
rangetest@localhost- explain analyze select * from some_data where
'[2010-01-01,2010-02-01)'::daterange @ whensit;
QUERY PLAN
pg...@j-davis.com (Jeff Davis) writes:
On Wed, 2011-02-09 at 16:20 -0500, Chris Browne wrote:
rangetest@localhost- explain analyze select * from some_data where
'[2010-01-01,2010-02-01)'::daterange @ whensit;
QUERY PLAN
2011/2/9 amit sehas cu...@yahoo.com:
Lets say that the cost based optimizer determines that the order of the
joins should be T1.a=T2.b followed by T2.c = T3.d followed by T3.e = T4.f
the question we have is during query execution are the joins evaluated
completely one by one in that order,
amit sehas cu...@yahoo.com wrote:
We are making some performance measurements, we are trying to
determine query execution behavior.
I hope you're not doing this on an un-tuned server or toy tables.
There are a number of configuration parameters which should be tuned
for your particular
I find that pg_upgrade fails in HEAD when asked to do a 9.1-to-9.1
upgrade of the regression database. It gets to this bit of the
restore script:
CREATE TABLE test_tbl2 OF public.test_type2;
-- For binary upgrade, recreate dropped column.
UPDATE pg_catalog.pg_attribute
SET attlen = -1, attalign
On Wed, Feb 9, 2011 at 6:30 PM, Peter Eisentraut pete...@gmx.net wrote:
The lastest clang svn tip (2.9-to-be, I guess) builds PostgreSQL out of
the box and most tests pass. Specifically, it no longer chokes on
-D_GNU_SOURCE on Linux, which was the previously reported blocker.
Odd, I tried the
On 11-02-09 05:22 PM, Peter Eisentraut wrote:
On tis, 2011-02-08 at 00:32 -0500, Steve Singer wrote:
On 11-02-06 11:40 AM, Jan Urbański wrote:
PFA an updated patch with documentation.
Yeah, changed them.
Those changes look fine. The tests now pass.
I've attached a new version of the patch
Trivial patch attached.
-Kevin
*** a/doc/src/sgml/mvcc.sgml
--- b/doc/src/sgml/mvcc.sgml
***
*** 604,610 ERROR: could not serialize access due to read/write
dependencies among transact
Consistent use of Serializable transactions can simplify development.
The
On Thu, Feb 10, 2011 at 09:30, Kevin Grittner
kevin.gritt...@wicourts.gov wrote:
Trivial patch attached.
Applied. Thanks!
--
Itagaki Takahiro
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
Dimitri Fontaine wrote:
Tom Lane t...@sss.pgh.pa.us writes:
In any case that would ratchet the priority of ALTER EXTENSION UPGRADE
back up to a must-have-for-9.1, since pg_upgrade would then leave you
with a non-upgraded extension.
Now what?
What would be the problem with pg_upgrade
On Wed, Feb 9, 2011 at 5:25 AM, Robert Haas robertmh...@gmail.com wrote:
On Tue, Feb 8, 2011 at 2:34 PM, Magnus Hagander mag...@hagander.net wrote:
I also agree with the general idea of trying to break it into smaller
parts - even if they only provide small parts each on it's own. That
also
On Wed, Feb 9, 2011 at 7:02 PM, Magnus Hagander mag...@hagander.net wrote:
On Thu, Feb 3, 2011 at 11:19, Magnus Hagander mag...@hagander.net wrote:
On Wed, Feb 2, 2011 at 18:00, Magnus Hagander mag...@hagander.net wrote:
On Wed, Feb 2, 2011 at 17:43, Heikki Linnakangas
Tom Lane wrote:
I find that pg_upgrade fails in HEAD when asked to do a 9.1-to-9.1
upgrade of the regression database. It gets to this bit of the
restore script:
CREATE TABLE test_tbl2 OF public.test_type2;
-- For binary upgrade, recreate dropped column.
UPDATE pg_catalog.pg_attribute
On ons, 2011-02-09 at 18:43 -0500, Tom Lane wrote:
I find that pg_upgrade fails in HEAD when asked to do a 9.1-to-9.1
upgrade of the regression database. It gets to this bit of the
restore script:
CREATE TABLE test_tbl2 OF public.test_type2;
-- For binary upgrade, recreate dropped
On ons, 2011-02-09 at 23:16 -0500, Bruce Momjian wrote:
I am not aware of this code changing in 9.1. Was this test in 9.0?
Does this problem happen for 9.0?
No, because you can't drop anything from a typed table in 9.0.
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
strk s...@keybit.net writes:
I've finally completed the debugging phase and have
a minimal self-contained testcase showing the problem.
It has to do with INITIALLY DEFERRED constraints.
I looked into this and find that the issue is you're trying to drop a
table that has unfired AFTER TRIGGER
On Thu, Feb 10, 2011 at 12:03:49AM -0500, Tom Lane wrote:
strk s...@keybit.net writes:
I've finally completed the debugging phase and have
a minimal self-contained testcase showing the problem.
It has to do with INITIALLY DEFERRED constraints.
I looked into this and find that the issue
This commit refers to www.mingw64.org which does not exist.
Also, clicking on the gitweb link below (from GMail), opens the browser
window with an address where ';' are replaced with %3B , which leads to 404
- no such project. Is GMail broken, or can have gitweb treat %3B as a ; ?
Regards,
On
On Sat, Feb 05, 2011 at 10:59:45PM +0100, Rados??aw Smogura wrote:
I do performance tests against orignal JDBC driver and my version in binary
and in text mode. I saw strange results when I was reading varchar values.
Here is some output from simple benchmark
Plain strings speed
On Wed, 2011-02-09 at 18:07 -0500, Chris Browne wrote:
rangetest@localhost- create index i2 on some_data (range(whensit));
CREATE INDEX
If you make this a GiST index, it should work.
The rewrites so that it can use a btree are an interesting idea though.
Regards,
Jeff Davis
--
On Sat, Feb 5, 2011 at 4:59 PM, Radosław Smogura
rsmog...@softperience.eu wrote:
Hi,
I do performance tests against orignal JDBC driver and my version in binary
and in text mode. I saw strange results when I was reading varchar values.
Here is some output from simple benchmark
Plain strings
Actually difference is
http://archives.postgresql.org/pgsql-hackers/2011-02/msg00415.php
Merlin Moncure mmonc...@gmail.com Thursday 10 February 2011 08:48:26
On Sat, Feb 5, 2011 at 4:59 PM, Radosław Smogura
rsmog...@softperience.eu wrote:
Hi,
I do performance tests against orignal JDBC
88 matches
Mail list logo
