Hi Monty,
Would you be able to update the MySQL manual?
In 1.9.2.3 of the MySQL manual
(http://www.mysql.com/doc/en/MySQL-PostgreSQL_benchmarks.html) it
mentions :
"The only Open Source benchmark that we know of that can be used to
benchmark MySQL Server and PostgreSQL (and other databases) is
% uname -a
FreeBSD xor 4.6-STABLE FreeBSD 4.6-STABLE #2: Tue Jun 18 20:48:48 MSD 2002
teodor@xor:/usr/src/sys/compile/XOR i386
...
gmake[3]: `/spool/home/teodor/pgsql/src/backend/commands'
gcc -g -O -Wall -Wmissing-prototypes -Wmissing-declarations
-I../../../src/include -c -o aggregatecmds
Hiya Lists
Somebody could help me? I am with an error when the Postgresql makes Insert,
Delete or Update
kernel: SCSI disk error : host 2 channel 0 id 0 lun 0 return code = 7
kernel: I/O error: dev 08:08, sector 47938856
kernel: SCSI disk error : host 2 channel 0 id 0 lun 0 return co
On Fri, 20 Sep 2002, Ricardo Fogliati wrote:
> Hiya Lists
>
> Somebody could help me? I am with an error when the Postgresql makes Insert,
> Delete or Update
>
> kernel: SCSI disk error : host 2 channel 0 id 0 lun 0 return code = 7
> kernel: I/O error: dev 08:08, sector 47938856
> k
Thanks for the explanation.
On Thu, Sep 19, 2002 at 03:46:05PM -0400, Jan Wieck wrote:
> Someone might think now it'd be at least handy to have a mechanism to
> enforce parsing of all expressions and queries for debugging purposes.
> But that's not that easy. As soon as you use for example a reco
gborg
On Fri, 20 Sep 2002, Justin Clift wrote:
> Hi everyone,
>
> Have gotten a new PostgreSQL utility together called "pg_autotune" that
> load tests using Tatsuo's pgbench code over multiple-iterations,
> attempting to determine decent buffer settings for a specified client
> load.
>
> It's m
Teodor Sigaev <[EMAIL PROTECTED]> writes:
> gcc -g -O -Wall -Wmissing-prototypes -Wmissing-declarations
> -I../../../src/include -c -o copy.o copy.c
> copy.c: In function `CopyFrom':
> copy.c:1130: warning: passing arg 1 of `coerce_type_constraints' from
> incompatible pointer type
> copy.c:11
On Fri, Sep 20, 2002 at 01:32:52PM +0100, Nigel J. Andrews wrote:
> the hardware. On the other hand I do believe I saw a message
> recently saying that some of the 2.4 series kernels had file system
> bugs.
I recall problems, offhand, with 2.4.5, 2.4.10, 2.4.11 (which was so
broken that you coul
Well, you'll probably want to pass in a valid timeval structure if you
don't want it to block.
Basically, that snippet tells select on the list of sockets, looking for
sockets that have data to be read while waiting forever. That means it
will block until something appears on one of the sockets
Hi Greg,
That's cool. Played with it for a while longer, then found out that the
order that it was being called in didn't work very well as the select()
was executed after all the required sockets had been closed/ended.
So, it just meant a re-ordering of things, and it's now working alright.
A
Hi all,
While testing for large databases, I am trying to load 12.5M rows of data from
a text file and it takes lot longer than mysql even with copy.
Mysql takes 221 sec. v/s 1121 sec. for postgres. For postgresql, that is around
11.5K rows per second. Each tuple has 23 fields with fixed lengt
Ensure you don't have termination issues. Make sure your SCSI interface
is configured correctly for your SCSI environment, especially on matters
of termination. Make sure you have enough power to your drive and if
possible, make sure your drives are hung off of distinct power segments
coming fro
Are you using copy within a transaction?
I don't know how to explain the size difference tho. I have never seen an
overhead difference that large. What type of MySQL tables were you using
and what version?
Have you tried this with Oracle or similar commercial database?
-Original Message--
On 20 Sep 2002 at 21:22, Shridhar Daithankar wrote:
> Mysql takes 221 sec. v/s 1121 sec. for postgres. For postgresql, that is around
> 11.5K rows per second. Each tuple has 23 fields with fixed length of around 100
> bytes
>
> I wrote a programs which does inserts in batches but none of thme
http://developer.novell.com/connections/091902.html
I'm somehwat surprized no one else has mentioned this, as it's on Slashdot...
--
Lamar Owen
WGCR Internet Radio
1 Peter 4:11
---(end of broadcast)---
TIP 5: Have you checked our extensive FAQ?
h
On 20 Sep 2002 at 10:26, Jonah H. Harris wrote:
> Also, did you disable fsync?
Aarrrgggh.. If that turns out to be culprit, I will kill him..;-)
Problem is I can't see postgresql.conf nor can access his command history and
he has left for the day..
I will count that in checklist but this is p
On 20 Sep 2002 at 10:14, Jonah H. Harris wrote:
> Are you using copy within a transaction?
No. Will that help? I can try. But the utility I wrote, I could insert say 10K
records in a transaction. Copy seems to be doing it all in one transaction. I
don't get any value for select count(*) in ano
Also, did you disable fsync?
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]On Behalf Of Jonah H. Harris
Sent: Friday, September 20, 2002 10:15 AM
To: [EMAIL PROTECTED]; [EMAIL PROTECTED]
Subject: Re: [HACKERS] Improving speed of copy
Are you using copy within a tr
On Fri, 2002-09-20 at 08:52, Shridhar Daithankar wrote:
> Besides there is issue of space. Mysql takes 1.4GB space for 1.2GB text data
> and postgresql takes 3.2GB of space. Even with 40 bytes per row overhead
> mentioned in FAQ, that should come to around 1.7GB, counting for 40% increase
> in
On Fri, 20 Sep 2002, Shridhar Daithankar wrote:
> In select test where approx. 15 rows where reported with query on index field,
> mysql took 14 sec. and psotgresql took 17.5 sec. Not bad but other issues
> eclipse the result..
I don't know about anyone else but I find this aspect strange. Tha
On 20 Sep 2002, Greg Copeland wrote:
> I'll try to have a look-see by the end of the weekend. Any code that
> can reproduce it or is it ANY code that uses SPI?
>
> Greg
>
>
> On Fri, 2002-09-20 at 11:39, Peter Eisentraut wrote:
> > Tom Lane writes:
> >
> > > On looking a little more closely,
On Thu, 19 Sep 2002, Kris Jurka wrote:
>
> On Thu, 19 Sep 2002, Tom Lane wrote:
>
> > Kris Jurka <[EMAIL PROTECTED]> writes:
> > > While adding schema support to the JDBC Driver, I came across a query
> > > which occasionally generates some spectacularly bad plans.
> >
> > Hm, does an ANALYZE he
Nigel J. Andrews wrote:
> On Fri, 20 Sep 2002, Shridhar Daithankar wrote:
>
>>In select test where approx. 15 rows where reported with query on index field,
>>mysql took 14 sec. and psotgresql took 17.5 sec. Not bad but other issues
>>eclipse the result..
>
> I don't know about anyone else but
Karel Zak writes:
> test=# select to_char(0,'FM9.9');
> to_char
> -
> 0.
> (1 row)
>
> test=# select to_char(1,'FM9.9');
> to_char
> -
> 1.
> (1 row)
I find this highly bizzare. The FM modifier means to omit unnecessary
trailing stuff. There is no reasonable business or sci
Kris Jurka <[EMAIL PROTECTED]> writes:
> Looking at the differences in statistics before and after the ANALYZE the
> only differences are in correlation. This comes from initdb around line
> 1046...
> "$PGPATH"/postgres $PGSQL_OPT template1 >/dev/null < ANALYZE;
> VACUUM FULL FREEZE;
> EOF
> Co
Hello -- I'm the lead programmer of Lyris ListManager, an email list server that run
on PostgreSQL, Oracle, and MS/SQL.
About 20% of our client base of 4000 runs on PostgresSQL -- it's very popular with our
clients -- much more than Oracle is (about 3%).
Unfortunately we have about a dozen cli
John Buckman <[EMAIL PROTECTED]> writes:
> It seems that with larger database sizes (500,000 rows and larger) and
> high stress, the server daemon has a tendency to core.
We'd love to see some stack traces ...
regards, tom lane
---(end of broadcas
Ok, below is the original email I sent, which I can not remember seeing come
across the patches list. Please do read the assumptions since they might throw
up problems with what I have done.
I have attached the pltcl patch again, just in case. For the sake of clarity
let's say this patch supersc
As a result of some disk errors on another drive, an admin in our group
brought down the server hosting our pgsql databases with a kill -KILL
after having gone to runlevel 1 and finding the postmaster process still
running. No surprise, our installation was hosed in the process.
After talking on
Tom Lane dijo:
> I think we could make all these cases work if we replaced attisinherited
> with *two* columns, a boolean attislocal(ly defined) and a count of
> (direct) inheritances. DROP ONLY would have the effect of decrementing
> the count and setting attislocal to true in each direct chil
Peter Eisentraut <[EMAIL PROTECTED]> writes:
> Karel Zak writes:
>> test=# select to_char(0,'FM9.9');
>> to_char
>> -
>> 0.
>> (1 row)
>>
>> test=# select to_char(1,'FM9.9');
>> to_char
>> -
>> 1.
>> (1 row)
> I find this highly bizzare.
No doubt, but it's what Oracle does (see
Is there ever a need to have more than one conversion for a given
combination of encodings? And if I have more than one combination
registered, which one is used by the implicit server/client conversion?
Also, if my server encoding is A and my client encoding is B, and I do
SELECT convert('some
On Thu, 19 Sep 2002, Thomas Lockhart wrote:
> Actually, a core member did implement this just a few weeks ago. The
> same crew arguing this time rejected the changes and removed them from
> the 7.3 feature set.
The change to make a PG_XLOG environment variable was rejected. Is that
really the ch
Tom Lane kirjutas R, 20.09.2002 kell 04:49:
> Bruce Momjian <[EMAIL PROTECTED]> writes:
> > Christopher Kings-Lynne wrote:
> >> Has anyone given much thought as to perhaps we could just drop multiple
> >> inheritance from Postgres?
>
> > I am for it. Multiple inheritance is more of a mess than a
Hannu Krosing <[EMAIL PROTECTED]> writes:
> I still think that this should be fixed in 7.3, but the inhcount
> attribute should show all tables where the column is defined, not just
> inherited. The default, no-inheritance case should set the column to 1.
Well, no, because then a locally defined
> -Original Message-
> From: Marc G. Fournier [mailto:[EMAIL PROTECTED]]
> Sent: 20 September 2002 14:55
> To: Justin Clift
> Cc: PostgreSQL Hackers Mailing List
> Subject: Re: [HACKERS] Where to post a new PostgreSQL utility?
>
>
>
> gborg
Just because I'm curious, is *all* new stu
> Is there ever a need to have more than one conversion for a given
> combination of encodings?
Sure. For example, several Unicode and SJIS mappings exist depending
on vendors or standards. M$ has its own, Apple has another one...
If a user want to employ Apple's map, he could define his own impl
Dave Page writes:
> Just because I'm curious, is *all* new stuff going to Gborg, and is the
> existing /contrib going to migrated there?
I'm curious too...
If that is to happen then the profile of gborg would need to be
massively increased. Currenly the only real link on the 'net to gborg
(by
"Christopher Kings-Lynne" <[EMAIL PROTECTED]> writes:
> The sessions table holds normal site session data, like a uid, username,
> some other stuff, etc. However entries older than two hours or so get
> deleted. We VACUUM everynight, so why is the on-disk relation growing so
> huge?
FSM not big
> -Original Message-
> From: Lee Kindness [mailto:[EMAIL PROTECTED]]
> Sent: 20 September 2002 15:19
> To: Dave Page
> Cc: Marc G. Fournier; Justin Clift; Lee Kindness; PostgreSQL
> Hackers Mailing List
> Subject: Re: [HACKERS] Where to post a new PostgreSQL utility?
>
>
> Dave Page
Stephan Szabo <[EMAIL PROTECTED]> writes:
> ... let you do the replace and keep reading (at the penalty that
> you've now got to have a way to know when to remove the
> various s)
That is the hard part. Mike's description omitted one crucial step:
6. The old "foo" goes away when the last open f
I don't think we are not going to be supporting Win9X so there isn't an
issue there. We will be supporting Win2000/NT/XP.
I don't understand FILE_SHARE_DELETE. I read the description at:
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/fileio/base/createfile.asp
but
Bruce Momjian wrote:
> I don't think we are not going to be supporting Win9X so there isn't an
> issue there. We will be supporting Win2000/NT/XP.
>
> I don't understand FILE_SHARE_DELETE. I read the description at:
>
>
>http://msdn.microsoft.com/library/default.asp?url=/library/en-us/f
On Fri, 20 Sep 2002, Mike Mascari wrote:
> Bruce Momjian wrote:
> > I don't think we are not going to be supporting Win9X so there isn't an
> > issue there. We will be supporting Win2000/NT/XP.
> >
> > I don't understand FILE_SHARE_DELETE. I read the description at:
> >
> >
>http://msdn.mi
Tom Lane wrote:
> Teodor Sigaev <[EMAIL PROTECTED]> writes:
> > gcc -g -O -Wall -Wmissing-prototypes -Wmissing-declarations
> > -I../../../src/include -c -o copy.o copy.c
> > copy.c: In function `CopyFrom':
> > copy.c:1130: warning: passing arg 1 of `coerce_type_constraints' from
> > incompati
It is good that moving the file out of the way works, but it doesn't
completely solve the problem.
What we have now with Unix rename is ideal:
1) old opens continue seeing the old contents
2) new opens see the new contents
3) the file always exists under the fixed name
Mike Mascari wrote:
> Bruce Momjian wrote:
> > I don't think we are not going to be supporting Win9X so there isn't an
> > issue there. We will be supporting Win2000/NT/XP.
> >
> > I don't understand FILE_SHARE_DELETE. I read the description at:
> >
> >
>http://msdn.microsoft.com/library/
Tom Lane wrote:
> Teodor Sigaev <[EMAIL PROTECTED]> writes:
> > gcc -g -O -Wall -Wmissing-prototypes -Wmissing-declarations
> > -I../../../src/include -c -o copy.o copy.c
> > copy.c: In function `CopyFrom':
> > copy.c:1130: warning: passing arg 1 of `coerce_type_constraints' from
> > incompati
Mike Mascari wrote:
> instead of fopen(). I'm not sure about ME, but I suspect it
> behaves similarly to 95/98.
I just checked with Katie and the good news (tm) is that the Win32 port
we did here at PeerDirect doesn't support 95/98 and ME anyway. It does
support NT4, 2000 and XP. So don't bother
Bruce Momjian <[EMAIL PROTECTED]> writes:
> OK, patch attached. Tom, what is the proper third parameter in COPY,
> COERCE_DONTCARE?
It would be COERCE_IMPLICIT_CAST. But I don't like the patch as it
stands anyway, because it is repeating a ton of catalog lookups for
every input row. I have more
Tom Lane wrote:
> Bruce Momjian <[EMAIL PROTECTED]> writes:
> > OK, patch attached. Tom, what is the proper third parameter in COPY,
> > COERCE_DONTCARE?
>
> It would be COERCE_IMPLICIT_CAST. But I don't like the patch as it
> stands anyway, because it is repeating a ton of catalog lookups for
>
Bruce Momjian <[EMAIL PROTECTED]> writes:
> I think we may be best just looping on MoveFileEx() until is succeeds.
> We do the pg_pwd writes while holding an exclusive lock on pg_shadow so
> that will guarantee that no one else will slip an old version of the
> file in after we have written it.
Stephan Szabo wrote:
> On Fri, 20 Sep 2002, Mike Mascari wrote:
>
>
>>I think that's a rather poor description. I think it just means
>>that if the file is opened once via CreateFile() with
>>FILE_SHARE_DELETE, then any subsequent CreateFile() calls will
>>fail unless they too have FILE_SHARE_DE
Tom Lane wrote:
> Bruce Momjian <[EMAIL PROTECTED]> writes:
> > I think we may be best just looping on MoveFileEx() until is succeeds.
> > We do the pg_pwd writes while holding an exclusive lock on pg_shadow so
> > that will guarantee that no one else will slip an old version of the
> > file in a
It seems the 'numeric' and 'int8' tests are failing in CVS HEAD. The
culprit seems to be the recent to_char() change made by Karel, but I
haven't verified that. The diff follows.
Cheers,
Neil
--
Neil Conway <[EMAIL PROTECTED]> || PGP Key ID: DB3C29FC
*** ./expected/int8.out Fri Jan 26 17:50:2
Tom Lane writes:
> On looking a little more closely, it's clear that pltcl_SPI_exec()
> should be, and is not, calling SPI_freetuptable() once it's done with
> the tuple table returned by SPI_exec(). This needs to be done in all
> the non-elog code paths after SPI_exec has returned SPI_OK_SELECT
I wrote:
> Stephan Szabo wrote:
>>
>> The question is, what happens if two people have the file open
>> and one goes and tries to delete it? Can the other still read
>> from it?
>
> Yes. I just tested it and it worked. I'll test Bruce's scenario as well:
>
> foo contains: "FOO"
> bar contains:
Tom has fixed it. Sorry I didn't test earlier.
---
Neil Conway wrote:
> It seems the 'numeric' and 'int8' tests are failing in CVS HEAD. The
> culprit seems to be the recent to_char() change made by Karel, but I
> haven't
Mike Mascari wrote:
> Its interesting in that it allows for Unix-style rename() and
> unlink() behavior, but with a race condition. Without Stephan's
> two MoveFile() trick and the FILE_SHARE_DELETE flag, however,
> the result would be Access Denied. Are the places in the backend
> that use re
Mike Mascari wrote:
> > foo contains: "FOO"
> > bar contains: "BAR"
> >
> > 1. Process 1 opens "foo"
> > 2. Process 2 opens "foo"
> > 3. Process 1 calls MoveFile("foo", "foo2");
> > 4. Process 3 opens "foo" <- Successful?
> > 5. Process 1 calls MoveFile("bar", "foo");
> > 6. Process 4 opens "foo"
I'll try to have a look-see by the end of the weekend. Any code that
can reproduce it or is it ANY code that uses SPI?
Greg
On Fri, 2002-09-20 at 11:39, Peter Eisentraut wrote:
> Tom Lane writes:
>
> > On looking a little more closely, it's clear that pltcl_SPI_exec()
> > should be, and is no
Thomas Lockhart wrote:
> ...
> > Why you object to that, and insist it must be an environment variable
> > instead (if that is indeed what you're doing), I'm not sure
>
> Well, what I was hoping for, but no longer expect, is that features
> (store xlog in another area) can be implemented and
Hello!
i'm using PostgreSQL 7.2.1 and got strange parse errors..
could somebody tell me what's wrong with this timestamp query example?
PostgreSQL said: ERROR: parser: parse error at or near "date"
Your query:
select timestamp(date '1998-02-24', time '23:07')
example is from PostgreSQL help an
On Fri, 20 Sep 2002, Tomas Lehuta wrote:
> Hello!
>
> i'm using PostgreSQL 7.2.1 and got strange parse errors..
> could somebody tell me what's wrong with this timestamp query example?
>
> PostgreSQL said: ERROR: parser: parse error at or near "date"
> Your query:
>
> select timestamp(date '1998-
"Tomas Lehuta" <[EMAIL PROTECTED]> writes:
> could somebody tell me what's wrong with this timestamp query example?
> select timestamp(date '1998-02-24', time '23:07')
> PostgreSQL said: ERROR: parser: parse error at or near "date"
> example is from PostgreSQL help
>From where exactly? I don't
65 matches
Mail list logo
