On Sun, Feb 25, 2001 at 12:41:28AM -0500, Tom Lane wrote:
> Attached are graphs from more thorough runs of pgbench with a commit
> delay that occurs only when at least N other backends are running active
> transactions. ...
> It's not entirely clear what set of parameters is best, but it is
> abso
At 00:42 25/02/01 -0800, Nathan Myers wrote:
>
>The only really bad performers were (0), (10k,1), (100k,20). The best
>were (30k,1) and (30k,10), although (30k,5) also did well except at 40.
>Why would 30k be a magic delay, regardless of siblings? What happened
>at 40?
>
I had assumed that 40 w
Hello.
I have made a small contribution to the JDBC driver, in the JDBC
v2.0 stuff. Whom do I send it to?
Ola
---
Ola Sundell
[EMAIL PROTECTED] - [EMAIL PROTECTED] - [EMAIL PROTECTED]
http://miranda.org/~ola
PGP key information:
pub 1024/744E6D8D 2000/02/13 Ola Sundell <[EMAIL PROTECTED]>
Key
At 05:07 PM 2/24/01 -0500, Tom Lane wrote:
>is not a defined concept according to SQL. Even if we allowed queries
>such as you've described, the results would not be well-defined, but
>would change at the slightest provocation. The implementation feels
>itself entitled to rearrange tuple order w
Roberto Mello writes:
> I wrote it in standard DocBook and would be glad to give it to the PG
> team if there's interest in including its whole or part in the
> documentation. Just let me know who should I send it to.
Send it to [EMAIL PROTECTED], either as a patch or as whatever you
have
> -Original Message-
> From: Tom Lane
>
> Attached are graphs from more thorough runs of pgbench with a commit
> delay that occurs only when at least N other backends are running active
> transactions.
>
> My initial try at this proved to be too noisy to tell much. The noise
> seems to
"Hiroshi Inoue" <[EMAIL PROTECTED]> writes:
> How about the case with scaling factor 1 ? i.e Could your
> proposal detect lock conflicts in reality ?
The code is set up to not count backends that are waiting on locks.
That is, to do a commit delay there must be at least N other backends
that are
Philip Warner <[EMAIL PROTECTED]> writes:
> At 00:42 25/02/01 -0800, Nathan Myers wrote:
>> The only really bad performers were (0), (10k,1), (100k,20). The best
>> were (30k,1) and (30k,10), although (30k,5) also did well except at 40.
>> Why would 30k be a magic delay, regardless of siblings?
Send it to the jdbc list please.
> Hello.
>
> I have made a small contribution to the JDBC driver, in the JDBC
> v2.0 stuff. Whom do I send it to?
>
> Ola
>
> ---
> Ola Sundell
> [EMAIL PROTECTED] - [EMAIL PROTECTED] - [EMAIL PROTECTED]
> http://miranda.org/~ola
> PGP key information:
> pub 1
[EMAIL PROTECTED] (Nathan Myers) writes:
> At low loads, it seems (100k,1) (brown +) did best by far, which seems
> very odd. Even more odd, it did pretty well at very high loads but had
> problems at intermediate loads.
In theory, all these variants should behave exactly the same for a
singl
Hi
I've tried to search the site, but no usable pages turned up.
My question is about monitoring PostgreSQL and if it turns out to be "down"
to notify a person to take action.
I'm surprised that I couldn't find anything about it. Does anyone have an
advice ? Anything that will fit into ordina
Lincoln Yeoh <[EMAIL PROTECTED]> writes:
> Would it then be fine to use update ... limit in the following scenario?
> I have a todo queue:
> create table todo ( task text, pid int default 0);
> The tasks are inserted into the todo table.
> Then the various worker processes do the following update
Tom Lane wrote:
>
> Philip Warner <[EMAIL PROTECTED]> writes:
> > At 00:42 25/02/01 -0800, Nathan Myers wrote:
> >> The only really bad performers were (0), (10k,1), (100k,20). The best
> >> were (30k,1) and (30k,10), although (30k,5) also did well except at 40.
> >> Why would 30k be a magic dela
Hi,
Is it desirable for me to build Solaris 8 SPARC packages (Solaris .pkg
format) of beta5?
I have experience in doing this.
Regards and best wishes,
Justin Clift
Database Administrator
Hiroshi Inoue <[EMAIL PROTECTED]> writes:
>> Yes, I assumed the same. I posted the script; could someone else make
>> the same run? We really need more than one test case ;-)
> I could find the sciript but seem to have missed your change
> about commit_siblings. Where could I get it ?
Er ... d
>> I could find the sciript but seem to have missed your change
>> about commit_siblings. Where could I get it ?
> Er ... duh ... I didn't commit it yet. Well, it's harmless enough
> as long as commit_delay defaults to 0, so I'll go ahead and commit.
In CVS now.
However, it might be well to wa
At 04:58 PM 25-02-2001 -0500, Tom Lane wrote:
>
>There's no LIMIT clause in UPDATE. You could do something like
Oh. I thought 7.1 had that.
> BEGIN
> SELECT taskid FROM todo WHERE pid = 0 FOR UPDATE LIMIT 1;
> UPDATE todo SET pid = $mypid WHERE taskid = $selectedid;
> CO
Oops I screwed up again. :)
I was actually right the first time my postgresql 7.0.3 was running with
fsync off. Due to my weird results I searched more thoroughly and found my
7.0.3's pg_options had a nofsync=1.
So 7.0.3 is twice as fast only with fsync off.
7.1beta4 snapshot - fsync.
./pgben
[ Send to hackers]
> I'd be willing to consider using mmap as a compile-time option if it
> can be shown to be a substantial performance win where it's available.
> (I suspect that's a very big "if".) If it's not a substantial win,
> I don't think we should accept the change --- the portability
On Sun, 25 Feb 2001, Kaare Rasmussen wrote:
> Hi
>
> I've tried to search the site, but no usable pages turned up.
>
> My question is about monitoring PostgreSQL and if it turns out to be "down"
> to notify a person to take action.
>
> I'm surprised that I couldn't find anything about it. Does an
Lincoln Yeoh <[EMAIL PROTECTED]> writes:
>> BEGIN
>> SELECT taskid FROM todo WHERE pid = 0 FOR UPDATE LIMIT 1;
>> UPDATE todo SET pid = $mypid WHERE taskid = $selectedid;
>> COMMIT
> This is very similar to what I'm testing out in 7.0.3 - except I'm
> currently trying "order by random" to preven
> Tatsuo Ishii wrote:
> >
> > Hi Teodorescu,
> >
> > I have made patches which enable pgaccess to input Japanese characters
> > in the table editing window. As you might know, to input Japanese
> > characters, we first type in "hiragana" then convert it to "kanji". To
> > make this proccess tran
At 11:16 PM 25-02-2001 -0500, Tom Lane wrote:
>
>Right. Only the first row is locked, but that doesn't help any. "order
>by random" sounds like it might be a good answer, if there aren't many
>rows that need to be sorted.
Yep. I'll just see what happens in the testing stages.
>> What would hap
Bruce Momjian <[EMAIL PROTECTED]> writes:
> It allows no backing store on disk. It is the BSD solution to SysV
> share memory. Here are all the BSDi flags:
> MAP_ANONMap anonymous memory not associated with any specific file.
> The file descriptor used for creating MAP
Bruce Momjian <[EMAIL PROTECTED]> writes:
> I have had this item on the TODO list for a while:
> * Use mmap() rather than SYSV shared memory(?)
> Should I remove it?
It's fine as long as it's got that question mark on it ;-).
I don't say we *shouldn't* do this, I'm just raising questions
th
> Bruce Momjian <[EMAIL PROTECTED]> writes:
> > It allows no backing store on disk. It is the BSD solution to SysV
> > share memory. Here are all the BSDi flags:
>
> > MAP_ANONMap anonymous memory not associated with any specific file.
> > The file descriptor used for
> >Basically, I am not sure how much we lose by doing the delay after
> >returning COMMIT, and I know we gain quite a bit by enabling us to group
> >fsync calls.
>
> If included, this should be an option only, and not the default option.
Sure it should never become the default, because the "D
> Bruce Momjian <[EMAIL PROTECTED]> writes:
> > I have had this item on the TODO list for a while:
> > * Use mmap() rather than SYSV shared memory(?)
> > Should I remove it?
>
> It's fine as long as it's got that question mark on it ;-).
> I don't say we *shouldn't* do this, I'm just raising
28 matches
Mail list logo
