On 20/09/10 09:48, Vaibhav Kaushal wrote:
1. PostgreSQL can be distributed freely according to the license terms. Can
it be sold (for a price) without changing anything in the source?
Yes.
You will have a hard time finding anyone to buy it, though, because you
can download it for free from th
May be this is the wrong place to ask the question. Still, answer me if
someone can or please redirect me to some place where it can be answered. My
questions are:
1. PostgreSQL can be distributed freely according to the license terms. Can
it be sold (for a price) without changing anything in the
On 19/09/10 01:20, Robert Haas wrote:
On Sat, Sep 18, 2010 at 5:42 PM, Josh Berkus wrote:
There are considerable benefits to having a standby registry with a
table-like interface. Particularly, one where we could change
replication via UPDATE (or ALTER STANDBY) statements.
I think that using
On 18/09/10 22:59, Robert Haas wrote:
On Sat, Sep 18, 2010 at 4:50 AM, Simon Riggs wrote:
Waiting might sound attractive. In practice, waiting will make all of
your connections lock up and it will look to users as if their master
has stopped working as well. (It has!). I can't imagine why anyon
I had a small play with this. Pretty cool to be able to track progress
for COPY and VACUUM jobs. For some reason I could never elicit any
numbers (other than the default Nan) for a query (tried 'SELECT count(*)
FROM pgbench_accounts' but figured aggregates probably don't qualify as
simple, and
Robert Haas writes:
> In view of the foregoing problems, I'd like to propose adding a new
> system view, tentatively called pg_comments, which lists all of the
> comments for everything in the system in such a way that it's
> reasonably possible to do further filtering out the output in ways
> tha
On Sat, Sep 18, 2010 at 02:20:53PM -0400 I heard the voice of
David Blewett, and lo! it spake thus:
>
> Sorry for top-posting... I was under the impression that git over http was
> just as efficient since 1.6.6 [1].
That's about talking over HTTP to a git server running as CGI; it
doesn't help if
Tom Lane wrote:
> Hey Bruce, how is it that this recent commit
> http://archives.postgresql.org/pgsql-committers/2010-02/msg00202.php
> replaced a $PostgreSQL$ CVS keyword with a $Id$ one?
>
> The commit message mentions an "existing *.pl conversion script",
> so I'm suspicious that somewhere ther
2010/8/19 Pavel Stehule :
> Hello
>
> I am sending a prototype implementation of functions median and
> percentile. This implementation is very simple and I moved it to
> contrib for this moment - it is more easy maintainable. Later I'll
> move it to core.
I've reviewed this patch.
* The patch ca
> I've designed a way to tune sync rep so it is usable and useful. And
> putting that feature into 9.1 costs very little, if anything. My patch
> to do this is actually smaller than any other attempt to implement this
> and I claim faster too. You don't need to use the per-transaction
> controls,
On Sun, Sep 19, 2010 at 6:38 PM, Daniele Varrazzo
wrote:
> On Sat, Sep 18, 2010 at 5:01 PM, Pavel Stehule
> wrote:
>> There are some bariers?
>
> I see none at a first glance. I just don't get the intricacies of the
> .xid() method suggested in the dbapi
> (http://www.python.org/dev/peps/pep-02
Devrim =?ISO-8859-1?Q?G=DCND=DCZ?= writes:
> Where does PGXS makefile get /usr/share/doc/pgsql/contrib directory
> from?
> While building 3rd party RPMs using PGXS, even if I specify docdir in
> Makefile, README.* files are installed to this directory, which breaks
> parallel installation path as
Sushant Sinha writes:
> For the headline generation to work properly, email/file/url/host need
> to become skip tokens. Updating the patch with that change.
I looked at this patch a bit. I'm fairly unhappy that it seems to be
inventing a brand new mechanism to do something the ts parser can
alre
Where does PGXS makefile get /usr/share/doc/pgsql/contrib directory
from?
While building 3rd party RPMs using PGXS, even if I specify docdir in
Makefile, README.* files are installed to this directory, which breaks
parallel installation path as of 9.0+
Speficially, I want to install READMEs
unde
On Sat, 2010-09-18 at 14:42 -0700, Josh Berkus wrote:
> > * Per-transaction control. Some transactions are important, others are not.
>
> Low priority.
> I see this as a 9.2 feature. Nobody I know is asking for it yet, and I
> think we need to get the other stuff right first.
I understand compl
On 19/09/10 16:48, Kevin Grittner wrote:
After tossing it around in my head for a bit, the only thing that I
see (so far) which might work is to maintain a *list* of
SERIALIZABLEXACT objects in memory rather than a using a hash table.
The recheck after releasing the shared lock and acquiring an
e
Applied.
---
Bruce Momjian wrote:
> Tom Lane wrote:
> > Bruce Momjian writes:
> > > + This means that UPDATE, DELETE, and SELECT can trigger space
> > > + reclamation, while INSERT ... VALUES cannot because it does not retr
Robert Haas writes:
> On Sat, Sep 18, 2010 at 6:35 PM, Robert Haas wrote:
>> On Sat, Sep 18, 2010 at 3:11 PM, Tom Lane wrote:
>>> This is at least inconsistent and at worst wildly misleading. ISTM
>>> we ought to adopt some combination of the following ideas:
>> I vote for this combination:
>>
Hello
2010/9/19 Daniele Varrazzo :
> On Sat, Sep 18, 2010 at 5:01 PM, Pavel Stehule
> wrote:
>> Hello
>>
>> who is psycopg maintainer, please?
>
> Here is one. The others can be usually mailed on the psycopg mailing
> list, which is currently down and being recovered.
>
>> Can somebody explains
On Sat, Sep 18, 2010 at 5:01 PM, Pavel Stehule wrote:
> Hello
>
> who is psycopg maintainer, please?
Here is one. The others can be usually mailed on the psycopg mailing
list, which is currently down and being recovered.
> Can somebody explains to me, why
> psycopg doesn't support twophase commi
Andrew Dunstan writes:
> On 09/19/2010 12:25 PM, Tom Lane wrote:
>> # We don't want to change line numbers, so we simply reduce the keyword
>> # string to the file pathname part. For example,
>> # $PostgreSQL: pgsql/src/port/unsetenv.c,v 1.12 2010/09/07 14:10:30 momjian
>> Exp $
>> # becomes
>>
On 09/19/2010 12:25 PM, Tom Lane wrote:
Pursuant to that, attached are proposed modified versions of the two
scripts involved.
#
# We don't want to change line numbers, so we simply reduce the keyword
# string to the file pathname part. For example,
# $PostgreSQL: pgsql/src/port/unsetenv.c
Hey Bruce, how is it that this recent commit
http://archives.postgresql.org/pgsql-committers/2010-02/msg00202.php
replaced a $PostgreSQL$ CVS keyword with a $Id$ one?
The commit message mentions an "existing *.pl conversion script",
so I'm suspicious that somewhere there is a script that wants to
I wrote:
> I looked a bit more at your pggit_migrate stuff. I'm not terribly happy
> with the proposed clean_keywords.pl script. I'd like it to reduce the
> $PostgreSQL$ thingies to the full pathname of the file, rather than
> try to remove all trace of them, eg
> * $PostgreSQL: pgsql/src/p
Heikki Linnakangas wrote:
> ISTM you never search the SerializableXactHash table using a hash
> key, except the one call in CheckForSerializableConflictOut, but
> there you already have a pointer to the SERIALIZABLEXACT struct.
> You only re-find it to make sure it hasn't gone away while you
> tr
On 08/12/2010 06:27 AM, David Fetter wrote:
+1 for putting it in core in 9.1 :)
There are times I really wish I could get object graphs, or at least
hierarchically nested object trees, of objects matching various
criteria. JSON might be a reasonable representation, and one that's
increasing
26 matches
Mail list logo
