Dann,
Thanks for your response. I thought I'd covered most of what your are
asking in my first message, but these results are weird enough that I
can understand you might not give me the benefit of the doubt and
without very explicit confirmation. To answer your questions:
YES the query each time
My problem with GEQO using a random number generator is that
non-deterministic behavior is really hard to debug, and problems can go
undiagnosed for ages. Frankly I would rather something fail all the
time, than it work most of the time and fail just now and then. Never
getting a good plan for a q
Chris Browne wrote:
There's a way that compressed filesystems might *help* with a risk
factor, here...
By reducing the number of disk drives required to hold the data, you
may be reducing the risk of enough of them failing to invalidate the
RAID array.
And one more way.
If neither your databas
On Fri, Oct 31, 2008 at 04:36:02PM -0400, Eric Schwarzenbach wrote:
> As I explained already (no pun intended) running the query using EXPLAIN
> makes the wild variation go away. So I cannot get explain results for a
> fast and for a slow execution.
EXPLAIN only determines and outputs the query pl
Scott Marlowe wrote:
> On Thu, Oct 30, 2008 at 4:01 PM, Gregory Stark <[EMAIL PROTECTED]> wrote:
> > "Scott Marlowe" <[EMAIL PROTECTED]> writes:
> >
> >> I'm sure this makes for a nice brochure or power point presentation,
> >> but in the real world I can't imagine putting that much effort into it
Eric Schwarzenbach <[EMAIL PROTECTED]> writes:
> Now ordinarily I would interpret this use of the word "random" loosely, to
> mean "arbitrarily" or "using some non-meaningful selection criteria". But
> given what I am seeing, this leads me to consider that "random" is meant
> literally, and that it
On Fri, 31 Oct 2008 17:08:52 +
Gregory Stark <[EMAIL PROTECTED]> wrote:
> >> Invisible under normal operation sure, but when something fails
> >> the consequences will surely be different and I can't see how
> >> you could make a compressed filesystem safe without a huge
> >> performance hit.
aravind chandu <[EMAIL PROTECTED]> writes:
> I am
> using this pqxx library for postgresql to run programs.The following is
> the query which i gave to store the data,here data.speed,data.heading
> are float values and data.ttime is timestamp .If i try to run this
> statement I end up w
"Scott Marlowe" <[EMAIL PROTECTED]> writes:
> On Fri, Oct 31, 2008 at 1:34 PM, Eric Schwarzenbach
> <[EMAIL PROTECTED]> wrote:
>> This is postgreslq 8.3, on Windows XP. The query joins about 17 tables
>> (without an explicit JOIN, just using the WHERE criteria) with a few
> OK, whether you use joi
On Fri, Oct 31, 2008 at 7:17 AM, Patricio Mora
<[EMAIL PROTECTED]> wrote:
> Scott Marlowe escribió:
>
> On Fri, Oct 31, 2008 at 5:00 AM, Patricio Mora
> <[EMAIL PROTECTED]> wrote:
> > > - postmaster (PostgreSQL) 7.4.5 (Update unviable due to application)
>
> > And this prevents you from updating to
On Fri, Oct 31, 2008 at 1:21 PM, Joseph S <[EMAIL PROTECTED]> wrote:
> Goboxe wrote:
>>
>> Hi,
>>
>> I just receive a new server with 5 x 73GB SAS harddisk.
>> I tried to maximize the total usable space when configure using RAID
>> 5.
>>
>> What I plan to do to configure all the 5 harddisks using R
On Fri, Oct 31, 2008 at 1:34 PM, Eric Schwarzenbach
<[EMAIL PROTECTED]> wrote:
> I've got a particular query that is giving me ridiculously erratic query
> performance. I have the SQL in a pgadmin query window, and from one
> execution to another, with no changes, the time it takes varies from
SNI
This is in a sense a followup to my post with subject "Wildly erratic
query performance".
The more I think about it the only thing that makes sense of my results
is if the query planner really WAS choosing my join order truly randomly
each time. I went digging into the manual and Section 49.3.1.
"
* Aidan Van Dyk <[EMAIL PROTECTED]> [081031 15:11]:
> How about something like the attached. It's been spun quickly, passed
> regression tests, and some simple hand tests on REL8_3_STABLE. It seem slike
> HEAD can't initdb on my machine (quad opteron with SW raid1), I tried a few
> revision in t
[EMAIL PROTECTED] ("Scott Marlowe") writes:
> I assume hardware failure rates are zero, until there is one. Then I
> restore from a known good backup. compressed file systems have little
> to do with that.
There's a way that compressed filesystems might *help* with a risk
factor, here...
By red
Hello,
I am
using this pqxx library for postgresql to run programs.The following is
the query which i gave to store the data,here data.speed,data.heading
are float values and data.ttime is timestamp .If i try to run this
statement I end up with an error below this query.Please help m
> -Original Message-
> From: [EMAIL PROTECTED] [mailto:pgsql-general-
> [EMAIL PROTECTED] On Behalf Of Eric Schwarzenbach
> Sent: Friday, October 31, 2008 12:35 PM
> To: pgsql-general@postgresql.org
> Subject: [GENERAL] Wildly erratic query performance
>
> I've got a particular query that
I've got a particular query that is giving me ridiculously erratic query
performance. I have the SQL in a pgadmin query window, and from one
execution to another, with no changes, the time it takes varies from
half a second to, well, at least 10 minutes or so at which point I give
up an cancel the
On Tue, Oct 28, 2008 at 07:13:38AM -0700,
Tim Bruce - Postgres <[EMAIL PROTECTED]> wrote
a message of 41 lines which said:
> Wouldn't it be better to add the line 'sudo su - postgres' as the
> entry (command) for the user(s) in the sudoers file?
Simpler, set the "runas" parameter:
jsmith ALL
Goboxe wrote:
Hi,
I just receive a new server with 5 x 73GB SAS harddisk.
I tried to maximize the total usable space when configure using RAID
5.
What I plan to do to configure all the 5 harddisks using RAID 5.
Windows operating system also will be installed the same RAID 5 ( I
going to have c:
* Aidan Van Dyk <[EMAIL PROTECTED]> [081031 15:11]:
> Archiving 00010012
> Archiving 00010013
> Archiving 00010014
> Archiving 00010017
> Archiving 00010018
> Archiving 00010
* Greg Smith <[EMAIL PROTECTED]> [081001 00:00]:
> The overhead of clearing out the whole thing is just large enough that it
> can be disruptive on systems generating lots of WAL traffic, so you don't
> want the main database processes bothering with that. A related fact is
> that there is a
On Fri, Oct 31, 2008 at 9:36 AM, Chris Butler <[EMAIL PROTECTED]> wrote:
> I've been having intermittent problems with our DB server (running
> postgresql 8.3.3) reaching its connection limit, all because of a SELECT
> statement that's stuck while sending data. This gets stuck because there's a
> t
Michelle Konzack wrote:
I have a table where I have a serialnumber which shuld be increased be
each INSERT. I know I can use max() to get the highest number, but how
can I use it in a INSERT statement?
There was a message for some month a message describing it on this list
but I do not find
Joao Ferreira wrote:
Have you considered installing directlly from CPAN ?
# perl -MCPAN -e 'install DBD::Pg;'
On Fri, 2008-10-31 at 09:20 -0400, Kevin Murphy wrote:
My life would be complete if it offered perl-DBD-Pg for CentOS 5!
Yes, but I prefer a package in this situation
Ivan Sergio Borgonovo <[EMAIL PROTECTED]> writes:
> On Fri, 31 Oct 2008 08:49:56 +
> Gregory Stark <[EMAIL PROTECTED]> wrote:
>
>> Invisible under normal operation sure, but when something fails the
>> consequences will surely be different and I can't see how you
>> could make a compressed fil
On Wed, Oct 29, 2008 at 4:46 PM, Matthew T. O'Connor <[EMAIL PROTECTED]>wrote:
> Noah Freire wrote:
>
>> <2008-10-29 11:09:03.453 PDT>DEBUG: 0: accounts: vac: 16697969
>> (threshold 650), anl: 16697969 (threshold 12048)
>> <2008-10-29 11:09:05.610 PDT>DEBUG: 0: accounts: vac: 16699
On Thu, Oct 30, 2008 at 8:53 PM, Matthew T. O'Connor <[EMAIL PROTECTED]>wrote:
> Noah Freire wrote:
>
>> On Wed, Oct 29, 2008 at 4:46 PM, Matthew T. O'Connor <[EMAIL
>> PROTECTED]> [EMAIL PROTECTED]>> wrote:
>>Is the table being excluded? (see the pg_autovacuum system table
>>settings)
>>
I too have used a symlink for some time (years) to put temp onto
dedicated disks without any problems. I am not sure if 8.3 is
different but I symlink the directory: base/pgsql_tmp
Aaron Thul
http://www.chasingnuts.com
On Fri, Oct 31, 2008 at 8:11 AM, Sam Mason <[EMAIL PROTECTED]> wrote:
> On
Hi,
On Fri, 2008-10-31 at 09:20 -0400, Kevin Murphy wrote:
> My life would be complete if it offered perl-DBD-Pg for CentOS 5!
We had an up2date package, but it broke many apps inside RHEL/CentOS 5,
so I removed EL-4 and EL-5 branches from SVN.
If you want, you can grab Fedora 9 SRPM and rebuil
On Thu, 2008-10-30 at 13:08 -0700, Alan Hodgson wrote:
> On Thursday 30 October 2008, Joao Ferreira gmail
> > During restore:
> > # vmstat
> > procs memory--- ---swap-- -io -system-- cpu
> > r b swpd free buff cache si so bi bo in cs us sy id wa
> > 3
I've been having intermittent problems with our DB server (running
postgresql 8.3.3) reaching its connection limit, all because of a SELECT
statement that's stuck while sending data. This gets stuck because there's a
transaction waiting to do an ALTER TABLE, then the subsequent SELECTs wait
for the
Hi,
I know it has been posted before, but it's been some time since that
and there has been no definitive (good) answer, so: has anyone been
able to build and use PL/Ruby with postgres 8.3 on windows? I have had
no problems on my linux machine, but now I need to get it working on
windows...
Thank
On Fri, Oct 31, 2008 at 3:01 PM, Alvaro Herrera
<[EMAIL PROTECTED]>wrote:
> Scott Marlowe escribió:
> > On Thu, Oct 30, 2008 at 7:37 PM, Alvaro Herrera
> > <[EMAIL PROTECTED]> wrote:
> > > Scott Marlowe escribió:
> > >
> > >> What is the torn page problem? Note I'm no big fan of compressed file
>
> I have a table where I have a serialnumber which shuld be increased be
> each INSERT. I know I can use max() to get the highest number, but how
> can I use it in a INSERT statement?
Have a look in the manual for the SERIAL data type.
For fields with a SERIAL data type, you can use DEFAULT in
pardon me, I didn't read the post - just judged it by subject really :)
you can also use keyward DEFAULT, so insert into foo(a) values(default);
But that's the whole point of DEFAULT in create table statement. If you
omit that column, it will be set to default value.
On Fri, 31 Oct 2008 08:49:56 +
Gregory Stark <[EMAIL PROTECTED]> wrote:
> "Scott Marlowe" <[EMAIL PROTECTED]> writes:
>
> > What is the torn page problem? Note I'm no big fan of
> > compressed file systems, but I can't imagine them not working
> > with databases, as I've seen them work quite
On Fri, Oct 31, 2008 at 03:30:44AM +0100, Michelle Konzack wrote:
> I have a table where I have a serialnumber which shuld be increased be
> each INSERT. I know I can use max() to get the highest number, but how
> can I use it in a INSERT statement?
Just don't mention the column. For example,
Scott Marlowe escribió:
> On Thu, Oct 30, 2008 at 7:37 PM, Alvaro Herrera
> <[EMAIL PROTECTED]> wrote:
> > Scott Marlowe escribió:
> >
> >> What is the torn page problem? Note I'm no big fan of compressed file
> >> systems, but I can't imagine them not working with databases, as I've
> >> seen the
# create table foo( a SERIAL );
NOTICE: CREATE TABLE will create implicit sequence "foo_a_seq" for serial
column "foo.a"
CREATE TABLE
# \d+ foo
Table "public.foo"
Column | Type | Modifiers | Description
+-+-+-
a | inte
Hello,
I have a table where I have a serialnumber which shuld be increased be
each INSERT. I know I can use max() to get the highest number, but how
can I use it in a INSERT statement?
There was a message for some month a message describing it on this list
but I do not find the message anymo
Hi Devrim,
Thanks for the awesome resource of yumpgsqlrpms.org.
My life would be complete if it offered perl-DBD-Pg for CentOS 5!
I'll look around for a src rpm.
-Kevin
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.post
Scott Marlowe escribió:
On Fri, Oct 31, 2008 at 5:00 AM, Patricio Mora
<[EMAIL PROTECTED]> wrote:
Hello all.
- postmaster (PostgreSQL) 7.4.5 (Update unviable due to application)
And this prevents you from updating to 7.4.22?
Thanks, I'll try it on my development env
On Fri, Oct 31, 2008 at 5:00 AM, Patricio Mora
<[EMAIL PROTECTED]> wrote:
> Hello all.
>
> - postmaster (PostgreSQL) 7.4.5 (Update unviable due to application)
And this prevents you from updating to 7.4.22?
> - Solaris 9
> - Sun Cluster 3.1.0
> - SUNWscPostgreSQL 3.1.0
>
> About 3 times each week
On Oct 31, 2008, at 6:30 AM, Jodok Batlogg wrote:
nevertheless i still have the problem that words with '/' are beeing
interpreted as file paths instead of words. any idea how i could tweak
this?
The easiest solution I found was to replace '/' with a space before
parsing the text.
John
On Fri, Oct 31, 2008 at 09:01:29AM +0100, Christian Schrrrder wrote:
> So I would like
> to use a faster disk for these temporary files, too, but I could not
> find where the temporary files are located. Is there a separate
> directory? I have found a "pgsql_tmp" directory inside of the database
On Thu, Oct 30, 2008 at 02:28:38PM -0700, Alan Hodgson wrote:
> On Thursday 30 October 2008, Joao Ferreira <[EMAIL PROTECTED]>
> wrote:
> > well. see for yourself... (360 RAM , 524 SWAP) that's what it is...
> > it supposed to be somewhat an embedded product...
>
> Clearly your hardware is yo
On Thu, Oct 30, 2008 at 11:53:48PM +0100, Thomas wrote:
> Here is the SQL I am working with:
> SELECT products.*, orders.response_code FROM "products" JOIN items ON
> products.id = items.product_id
> LEFT OUTER JOIN orders ON (items.order_id = orders.id AND
> orders.response_code = '0' AND orders
Sergio,
On Fri, 31 Oct 2008, Ivan Sergio Borgonovo wrote:
On Fri, 31 Oct 2008 13:10:20 +0300 (MSK)
Oleg Bartunov <[EMAIL PROTECTED]> wrote:
Jodok,
you got what's you defined. Please, read documentation.
In short, word doesn't indexed if it is not recognized by any
dictionaried from stack of
On Fri, 31 Oct 2008, Jodok Batlogg wrote:
hi oleg,
thanks for your quick response,
2008/10/31 Oleg Bartunov <[EMAIL PROTECTED]>:
Jodok,
you got what's you defined. Please, read documentation.
In short, word doesn't indexed if it is not recognized by any
dictionaried from stack of dictionarie
Hello all.
- postmaster (PostgreSQL) 7.4.5 (Update unviable due to application)
- Solaris 9
- Sun Cluster 3.1.0
- SUNWscPostgreSQL 3.1.0
About 3 times each week, the check_pgs function of the SUNWscPostgreSQL
bin/functios file, stops my Postgres database.
I enabled the cluster's monitor logs (D
On Fri, Oct 31, 2008 at 2:49 AM, Gregory Stark <[EMAIL PROTECTED]> wrote:
>
> "Scott Marlowe" <[EMAIL PROTECTED]> writes:
>
>> What is the torn page problem? Note I'm no big fan of compressed file
>> systems, but I can't imagine them not working with databases, as I've
>> seen them work quite reli
On Thu, Oct 30, 2008 at 9:43 PM, Tom Lane <[EMAIL PROTECTED]> wrote:
> "Scott Marlowe" <[EMAIL PROTECTED]> writes:
>> Sure, bash Microsoft it's easy. But it doesn't address the point, is
>> a database safe on top of a compressed file system and if not, why?
>
> It is certainly *less* safe than it
On Wed, Oct 29, 2008 at 9:18 PM, Kevin Galligan <[EMAIL PROTECTED]> wrote:
> I'm approaching the end of my rope here. I have a large database.
> 250 million rows (ish). Each row has potentially about 500 pieces of
> data, although most of the columns are sparsely populated.
>
*snip*
>
> So, went
On Fri, 31 Oct 2008 13:10:20 +0300 (MSK)
Oleg Bartunov <[EMAIL PROTECTED]> wrote:
> Jodok,
>
> you got what's you defined. Please, read documentation.
> In short, word doesn't indexed if it is not recognized by any
> dictionaried from stack of dictionaries. Put stemming dictionary
> at the end, w
hi oleg,
thanks for your quick response,
2008/10/31 Oleg Bartunov <[EMAIL PROTECTED]>:
> Jodok,
>
> you got what's you defined. Please, read documentation.
> In short, word doesn't indexed if it is not recognized by any
> dictionaried from stack of dictionaries. Put stemming dictionary at the end
Jodok,
you got what's you defined. Please, read documentation.
In short, word doesn't indexed if it is not recognized by any
dictionaried from stack of dictionaries. Put stemming dictionary at the end,
which recognizes everything.
Oleg
On Fri, 31 Oct 2008, Jodok Batlogg wrote:
we're using tsea
Hi Kevin,
I'm not deeply knowledgeable about PostgreSQL, but my guess is that 2 things
are doing you in:
(1) scanning all those nulls during SELECTs (even though PostgreSQL is
efficient at nulls, there are still tens or hundreds of billions of them)
(2) All those single-field indexes, and aggreg
"Scott Marlowe" <[EMAIL PROTECTED]> writes:
> What is the torn page problem? Note I'm no big fan of compressed file
> systems, but I can't imagine them not working with databases, as I've
> seen them work quite reliably under exhange server running a db
> oriented storage subsystem. And I can't
On 31 okt 2008, at 02.18, Greg Smith <[EMAIL PROTECTED]> wrote:
On Thu, 30 Oct 2008, Tom Lane wrote:
The real reason not to put that functionality into core (or even
contrib) is that it's a stopgap kluge. What the people who want this
functionality *really* want is continuous (streaming) log-
Christian Schröder wrote:
So I would like to use a faster disk for these temporary files, too,
but I could not find where the temporary files are located. Is there a
separate directory? I have found a "pgsql_tmp" directory inside of the
database directories ("base//pgsql_tmp"). Is this what I'm
Hi list,
I want to optimize the performance of our PostgreSQL 8.2 server. Up to
now the server has a raid1 where the whole database is located
(including tha WAL files). We will now move the database to a raid5
(which should be faster than the raid1) and will also move the WAL to a
separate di
If Pg truncated the WAL files before calling archive_command, and would
accept truncated WAL files on restore, that'd be really useful.
On second thought - that'd prevent reuse of WAL files, or at least force
the filesystem to potentially allocate new storage for the part that was
truncated.
we're using tsearch2 with the german dictionary
http://www.sai.msu.su/~megera/postgres/gist/tsearch/V2/dicts/ispell/ispell-german-compound.tar.gz
for fulltext search.
the indexing is configured as follows:
CREATE TEXT SEARCH DICTIONARY public.german (
TEMPLATE = ispell,
DictFile = german,
Jason Long wrote:
Greg Smith wrote:
On Thu, 30 Oct 2008, Tom Lane wrote:
The real reason not to put that functionality into core (or even
contrib) is that it's a stopgap kluge. What the people who want this
functionality *really* want is continuous (streaming) log-shipping, not
WAL-segment-at
65 matches
Mail list logo