In #postgresql on freenode, somebody ever mentioned that ZFS from
Solaris helps a lot to the performance of pgsql, so dose anyone have
information about that?
Steve Atkins wrote:
On May 7, 2007, at 2:55 PM, David Levy wrote:
Hi,
I am about to order a new server for my Postgres cluster. I w
Greg Smith <[EMAIL PROTECTED]> writes:
> Debian packages PostgreSQL in a fashion unique to it; it's arguable
> whether it's better or not (I don't like it), but going with that will
> assure your installation is a bit non-standard compared with most Linux
> installas.
What Debian has done is
Jim Nasby wrote:
On May 5, 2007, at 5:57 PM, Yudhvir Singh Sidhu wrote:
Problem: Vacuum times jump up from 45 minutes, or 1:30 minutes to 6+
hours overnight, once every 1 to 3 months.
Solutions tried: db truncate - brings vacuum times down. Reindexing
brings vacuum times down.
Does it jump
On Mon, 7 May 2007, David Levy wrote:
I am hesitating between Fedora Core 6, CentOS and Debian. Can anyone
help with this ?
Debian packages PostgreSQL in a fashion unique to it; it's arguable
whether it's better or not (I don't like it), but going with that will
assure your installation is a
I am using FC6 in production for our pg 8.2.4 DB server and am quite
happy with it.
The big advantage with FC6 for me was that the FC6 team seems to keep
more current with the latest stable revs of most OSSW (including
kernel revs!) better than any of the other major distros.
(Also, SE Linux
[EMAIL PROTECTED] wrote:
On Tue, 8 May 2007, Chris wrote:
David Levy wrote:
Hi,
I am about to order a new server for my Postgres cluster. I will
probably get a Dual Xeon Quad Core instead of my current Dual Xeon.
Which OS would you recommend to optimize Postgres behaviour (i/o
access, mu
On Tue, 8 May 2007, Chris wrote:
David Levy wrote:
Hi,
I am about to order a new server for my Postgres cluster. I will
probably get a Dual Xeon Quad Core instead of my current Dual Xeon.
Which OS would you recommend to optimize Postgres behaviour (i/o
access, multithreading, etc) ?
I a
David Levy wrote:
Hi,
I am about to order a new server for my Postgres cluster. I will
probably get a Dual Xeon Quad Core instead of my current Dual Xeon.
Which OS would you recommend to optimize Postgres behaviour (i/o
access, multithreading, etc) ?
I am hesitating between Fedora Core 6, CentO
On May 7, 2007, at 2:55 PM, David Levy wrote:
Hi,
I am about to order a new server for my Postgres cluster. I will
probably get a Dual Xeon Quad Core instead of my current Dual Xeon.
Which OS would you recommend to optimize Postgres behaviour (i/o
access, multithreading, etc) ?
I am hesitatin
Bill Moran wrote:
In response to "Joshua D. Drake" <[EMAIL PROTECTED]>:
David Levy wrote:
Hi,
I am about to order a new server for my Postgres cluster. I will
probably get a Dual Xeon Quad Core instead of my current Dual Xeon.
Which OS would you recommend to optimize Postgres behaviour (i/o
a
In response to "Joshua D. Drake" <[EMAIL PROTECTED]>:
> David Levy wrote:
> > Hi,
> >
> > I am about to order a new server for my Postgres cluster. I will
> > probably get a Dual Xeon Quad Core instead of my current Dual Xeon.
> > Which OS would you recommend to optimize Postgres behaviour (i/o
>
David Levy wrote:
Hi,
I am about to order a new server for my Postgres cluster. I will
probably get a Dual Xeon Quad Core instead of my current Dual Xeon.
Which OS would you recommend to optimize Postgres behaviour (i/o
access, multithreading, etc) ?
I am hesitating between Fedora Core 6, CentO
Hi,
I am about to order a new server for my Postgres cluster. I will
probably get a Dual Xeon Quad Core instead of my current Dual Xeon.
Which OS would you recommend to optimize Postgres behaviour (i/o
access, multithreading, etc) ?
I am hesitating between Fedora Core 6, CentOS and Debian. Can an
On May 5, 2007, at 5:57 PM, Yudhvir Singh Sidhu wrote:
Problem: Vacuum times jump up from 45 minutes, or 1:30 minutes to 6
+ hours overnight, once every 1 to 3 months.
Solutions tried: db truncate - brings vacuum times down.
Reindexing brings vacuum times down.
Does it jump up to 6+ hours j
Andreas Kostyrka <[EMAIL PROTECTED]> writes:
> Ambrus Wagner (IJ/ETH) wrote:
>> Is there a way to prevent PostgreSQL from doing a full sort on the result
>> set after the unions have been completed? Even if I write
>>
>> (select a,b,c,d,e from table1 order by a,b) union all
>> (select a,b,c,d,e f
"Andreas Kostyrka" <[EMAIL PROTECTED]> writes:
>> (select a,b,c,d,e from table1 order by a,b) union all
>> (select a,b,c,d,e from table2 order by a,b) union all
>> etc...
>> (select a,b,c,d,e from tablen order by a,b) order by a,b;
>>
>> PostgreSQL does not seem to realise (maybe it should not
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I think you'll have to stick with doing your sorting (or merging) in
your client. Don't think that PG recognizes the fact it's just a merge step.
Andreas
Ambrus Wagner (IJ/ETH) wrote:
> Dear All,
>
> I have several tables containing data sorted by 2
Dear All,
I have several tables containing data sorted by 2 keys (neither are keys in db
terms (not unique), however). I would like to retrieve all rows from all tables
sorted by the same keys, essentially merging the contents of the tables
together. While I am completely aware of sort order no
18 matches
Mail list logo
