On Tue, May 03, 2011 at 01:36:36PM +0900, Vlad Arkhipov wrote:
> Then I commited the both and the second one raised an exception:
> ERROR: could not serialize access due to read/write dependencies among
> transactions
> SQL state: 40001
>
> However the second transaction does not access the recor
Hi PostgreSQL Hackers,
When compiling PG with mingw-w64 the PGDLLEXPORT macro is blank.
Here is a patch that "fixes it for me." If this is correct, I'd
appreciate it will be applied to 9.0.x as well as HEAD.
--
Johann Oskarssonhttp://www.2ndquadrant.com/|[]
PostgreSQL
Josh Berkus writes:
> Tom, Alexander,
> So we are using gist_intbig_ops, so that's not the issue.
> Using pgstattuple might be a bit of a challenge. The client doesn't
> have it installed, and I can't pull it from Yum without also upgrading
> PostgreSQL, since Yum doesn't stock old versions AFAI
30.04.2011 22:18, Kevin Grittner wrote:
Vlad Arkhipov wrote:
29.04.2011 21:18, Kevin Grittner wrote:
Vlad Arkhipov wrote:
But even if it would work it would not help me anyways. Because
my constraint is much more complex and depends on other tables, I
cannot express it in t
> For filter purpose, could have the form a 32bits/64bits choice?
That would go into the "platform details" field.
Adding new fields in Googledocs is problematic, so I'd rather not add
one at this point, and spend my time on replacing it with a Django app
instead.
--
Josh Berkus
PostgreSQL Exp
Tom, Alexander,
So we are using gist_intbig_ops, so that's not the issue.
Using pgstattuple might be a bit of a challenge. The client doesn't
have it installed, and I can't pull it from Yum without also upgrading
PostgreSQL, since Yum doesn't stock old versions AFAIK.
Maybe we should consider m
On May 1, 2011, at 12:27 PM, Patrick Earl wrote:
> In ORMs like NHibernate, there are a few strategies for mapping
> inheritance to SQL. One of these is "Joined Subclass," which allows
> for the elimination of duplicate data and clean separation of class
> contents.
>
> With a class hierarchy suc
On Mon, May 02, 2011 at 09:27:08PM +0200, Magnus Hagander wrote:
> postgres=# DROP TABLE FOO;
> ERROR: "foo" is not a table
> HINT: Use DROP FOREIGN TABLE to remove a foreign table.
> postgres=# CREATE INDEX baz ON foo(bar);
> ERROR: "foo" is not a table
>
> To some, that would be confusing - f
On Mon, May 02, 2011 at 04:56:42PM -0300, Alvaro Herrera wrote:
> Excerpts from David Fetter's message of lun may 02 14:30:15 -0300 2011:
> > On Mon, May 02, 2011 at 12:15:09PM -0300, Alvaro Herrera wrote:
>
> > > I think it'd be good to have id attrs in all the sect2 sections of that
> > > chapte
Merlin Moncure writes:
> On Mon, May 2, 2011 at 11:09 AM, Tom Lane wrote:
>> I did a bit of testing of this and committed it with minor adjustments.
> Thanks for the attribution -- I hardly deserved it. One question
> though: ALLOC_CHUNK_FRACTION was put to four with the language 'We
> allow ch
Excerpts from David Fetter's message of lun may 02 14:30:15 -0300 2011:
> On Mon, May 02, 2011 at 12:15:09PM -0300, Alvaro Herrera wrote:
> > I think it'd be good to have id attrs in all the sect2 sections of that
> > chapter.
>
> By "that chapter," do you mean everything in func.sgml, or just th
On Mon, May 2, 2011 at 11:09 AM, Tom Lane wrote:
> Merlin Moncure writes:
>> On Tue, Apr 26, 2011 at 3:19 PM, Merlin Moncure wrote:
>>> On Tue, Apr 26, 2011 at 1:48 PM, Tom Lane wrote:
After chewing on that thought for a bit, it seems like an easy fix is to
modify AllocSetContextCreat
postgres=# DROP TABLE FOO;
ERROR: "foo" is not a table
HINT: Use DROP FOREIGN TABLE to remove a foreign table.
postgres=# CREATE INDEX baz ON foo(bar);
ERROR: "foo" is not a table
To some, that would be confusing - foo kind of is a table, just a
different kind. Should we have some HINT on that
2011/5/2 Josh Berkus :
> Hackers,
>
> I've replaced test-report-by-email with a GoogleDocs application for Beta1.
>
> The form for submitting test reports is here:
>
> https://spreadsheets.google.com/viewform?hl=en&formkey=dEh3WEwzOFhKWWw4dHdRS2VQTExRdVE6MQ&ifq
[... cut ...]
It's very good Josh.
Peter Eisentraut writes:
> On ons, 2011-02-09 at 20:30 +0200, Peter Eisentraut wrote:
>> Regression tests (world):
>>
>> --- src/test/regress/expected/float8.out
>> +++ src/test/regress/results/float8.out
>> @@ -384,7 +384,15 @@
>> SELECT '' AS bad, f.f1 * '1e200' from FLOAT8_TBL f;
>> ERROR: va
Hackers,
I've replaced test-report-by-email with a GoogleDocs application for Beta1.
The form for submitting test reports is here:
https://spreadsheets.google.com/viewform?hl=en&formkey=dEh3WEwzOFhKWWw4dHdRS2VQTExRdVE6MQ&ifq
The accumulated test reports are here:
https://spreadsheets.google.co
On ons, 2011-02-09 at 20:30 +0200, Peter Eisentraut wrote:
> Regression tests (world):
>
> --- src/test/regress/expected/float8.out
> +++ src/test/regress/results/float8.out
> @@ -384,7 +384,15 @@
> SELECT '' AS bad, f.f1 * '1e200' from FLOAT8_TBL f;
> ERROR: value out of range: overflow
> SEL
On Mon, May 02, 2011 at 12:15:09PM -0300, Alvaro Herrera wrote:
> Excerpts from David Fetter's message of lun may 02 10:58:37 -0300 2011:
> > On Mon, Apr 18, 2011 at 06:44:03PM -0300, Alvaro Herrera wrote:
>
> > > The sect2 they are in would need an id attribute for there to be a
> > > stable #-st
Sorry, wrong list.. apologizes.
Em 2 de maio de 2011 13:56, Dickson S. Guedes escreveu:
> Olá povo, tudo bem?
>
> Que tal ajudarmos a testar esta versão candidata?
>
> Visite [1] e [2] para mais informações
>
> [1] http://www.postgresql.org/developer/beta
> [2] http://wiki.postgresql.org/wiki/How
Olá povo, tudo bem?
Que tal ajudarmos a testar esta versão candidata?
Visite [1] e [2] para mais informações
[1] http://www.postgresql.org/developer/beta
[2] http://wiki.postgresql.org/wiki/HowToBetaTest
--
Dickson S. Guedes
mail/xmpp: gue...@guedesoft.net - skype: guediz
http://guedesoft.net
Il 02/05/11 18:20, Simon Riggs ha scritto:
I'm sure Gabriele can add those things as well - that also looks like
another 1 line change.
Yes, today we have performed some tests with that patch as well
(attached is version 2). The version 2 of the patch (which includes the
change Tom suggested
On Mon, May 2, 2011 at 5:20 PM, Simon Riggs wrote:
>> Yeah, it would help during the initial scan
>> of the old rel, but not during the sort or reindex steps.
>
> As Greg points out, the sort is not really of concern (for now).
Though I was surprised the reindex isn't an equally big problem. It
m
Excerpts from Alastair Turner's message of sáb abr 30 05:10:40 -0300 2011:
> Extending the history command (\s) sounds more promising
> \s- for a reverse ordered history
> \s[n] for the last n or n-from-last-th (\s1 different from \p in that
> it shows the last completed query not the one in progr
On Mon, May 2, 2011 at 3:37 PM, Tom Lane wrote:
> Simon Riggs writes:
>> I can't see the objection to replacing something inadvertently removed
>> in 9.0, especially since it is a 1 line patch and is accompanied by
>> copious technical evidence.
>
> I am not sure which part of "this isn't a subst
Merlin Moncure writes:
> On Tue, Apr 26, 2011 at 3:19 PM, Merlin Moncure wrote:
>> On Tue, Apr 26, 2011 at 1:48 PM, Tom Lane wrote:
>>> After chewing on that thought for a bit, it seems like an easy fix is to
>>> modify AllocSetContextCreate (around line 390 in HEAD's aset.c) so that
>>> allocCh
On Mon, May 2, 2011 at 3:37 PM, Tom Lane wrote:
> As for "copious technical evidence", I saw no evidence provided
> whatsoever that this patch really did anything much to fix the
> reported problem. Yeah, it would help during the initial scan
> of the old rel, but not during the sort or reindex s
Excerpts from David Fetter's message of lun may 02 10:58:37 -0300 2011:
> On Mon, Apr 18, 2011 at 06:44:03PM -0300, Alvaro Herrera wrote:
> > The sect2 they are in would need an id attribute for there to be a
> > stable #-style link.
>
> Please find attached a patch to fix this.
>
> I believe th
Excerpts from Bernd Helmle's message of sáb abr 30 19:40:00 -0300 2011:
>
>
> --On 30. April 2011 20:19:36 +0200 Gabriele Bartolini
> wrote:
>
> > I have noticed that during VACUUM FULL on reasonably big tables, replication
> > lag climbs. In order to smooth down the replication lag, I propose
Hi all,
Is it possible to add support for cross compiled PGXS modules to the
build system?
That is, when PG is cross compiled, a -pg_config is
also built for use with external modules?
I'm not adverse to submit a patch for this myself, but would like a
pointer in the general direction for it.
Simon Riggs writes:
> I can't see the objection to replacing something inadvertently removed
> in 9.0, especially since it is a 1 line patch and is accompanied by
> copious technical evidence.
I am not sure which part of "this isn't a substitute for what happened
before 9.0" you fail to understan
On Mon, Apr 18, 2011 at 06:44:03PM -0300, Alvaro Herrera wrote:
> Excerpts from David Fetter's message of lun abr 18 18:34:11 -0300 2011:
> > Folks,
> >
> > While readjusting pg_docbot's URLs for LEAST and GREATEST, I came
> > across an infelicity. They'd been tagged as
> > "http://www.postgresql
On Sat, Apr 30, 2011 at 03:13, Jaime Casanova wrote:
> On Thu, Feb 3, 2011 at 7:56 AM, Magnus Hagander wrote:
>> Include more status information in walsender results
>>
>> Add the current xlog insert location to the response of
>> IDENTIFY_SYSTEM
>
> why was this third field added to SYSTEM_IDENT
On Mon, May 2, 2011 at 7:44 AM, Greg Stark wrote:
> On Sun, May 1, 2011 at 9:31 PM, Simon Riggs wrote:
>> I don't think the performance of replication is at issue. This is
>> about resource control.
>>
>
> The unspoken question here is why would replication be affected by i/o
> load anyways? It's
I'm working with a client that uses Postgres on what amounts to an
appliance.
The database is therefore subject to occasional torture such as, in this
particular case, running out of disk space while performing a million
plus queries (of mixed varieties, many using plpgsql with exception
handling
On Sun, May 1, 2011 at 9:31 PM, Simon Riggs wrote:
> I don't think the performance of replication is at issue. This is
> about resource control.
>
The unspoken question here is why would replication be affected by i/o
load anyways? It's reading data file buffers that have only recently
been writt
35 matches
Mail list logo
