Re: [HACKERS] CommitDelay performance improvement

2001-02-24 Thread Tom Lane
Philip Warner <[EMAIL PROTECTED]> writes: > Don't suppose you could post the original data? Sure. regards, tom lane commit_delay = 0 commit_siblings = 1 CHECKPOINT transaction type: TPC-B (sort of) scaling factor: 10 number of clients: 1 number of transactions per client

Re: [HACKERS] CommitDelay performance improvement

2001-02-24 Thread Philip Warner
At 00:41 25/02/01 -0500, Tom Lane wrote: > >Comments anyone? > Don't suppose you could post the original data? Philip Warner| __---_ Albatross Consulting Pty. Ltd. |/ - \ (A.B.N. 75 008 659

Re: [HACKERS] CommitDelay performance improvement

2001-02-24 Thread 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 be coming from WAL checkpoints that occur during a run and pu

Re: [HACKERS] PL/SQL-to-PL/pgSQL-HOWTO + PL/pgSQL documentation

2001-02-24 Thread Tom Lane
Roberto Mello <[EMAIL PROTECTED]> writes: > I think I finished the HOWTO that I've been writing far a couple days. > The HTML version is at http://www.brasileiro.net/roberto/howto. The > document expalins the basic differences from Oracle's PL/SQL to > PoltgreSQL's PL/pgSQL and how to port a

[HACKERS] mmap for zeroing WAL log

2001-02-24 Thread Tom Lane
[ redirected to pgsql-hackers instead of -patches ] Matthew Kirkwood <[EMAIL PROTECTED]> writes: > On Sat, 24 Feb 2001, Bruce Momjian wrote: >> I am confused why mmap() is better than writing to a real file. > It isn't, except that it allows to initialise the logfile in > one syscall, without fi

Re: [HACKERS] CommitDelay performance improvement

2001-02-24 Thread Nathan Myers
On Sat, Feb 24, 2001 at 01:07:17AM -0500, Tom Lane wrote: > [EMAIL PROTECTED] (Nathan Myers) writes: > > I see, I had it backwards: N=0 corresponds to "always delay", and > > N=infinity (~0) is "never delay", or what you call zero delay. N=1 is > > not interesting. N=M/2 or N=sqrt(M) or N=log(

[HACKERS] PL/SQL-to-PL/pgSQL-HOWTO + PL/pgSQL documentation

2001-02-24 Thread Roberto Mello
Hi, I think I finished the HOWTO that I've been writing far a couple days. The HTML version is at http://www.brasileiro.net/roberto/howto. The document expalins the basic differences from Oracle's PL/SQL to PoltgreSQL's PL/pgSQL and how to port applications to Postgres. It comes w

Re: [HACKERS] offset and limit in update and subselect

2001-02-24 Thread Tom Lane
"Timothy H. Keitt" <[EMAIL PROTECTED]> writes: > Basically, I need to update rows by offset from the beginning of the > table. I think you'd better rethink your data design. Tuple order in a table is not a defined concept according to SQL. Even if we allowed queries such as you've described, t

Re: [HACKERS] pg_atoi() behavior change? Intentional?

2001-02-24 Thread Tom Lane
Adam Haberlach <[EMAIL PROTECTED]> writes: > ... one of the engineers has been writing some queries that > cast a text field to an int and take advantage of the > fact that we used to turn text fields with no digits into 0, > much as C's atoi function works. > The new behavior is to throw a

Re: [HACKERS] offset and limit in update and subselect

2001-02-24 Thread Timothy H. Keitt
I see this (subselect) is available in >=7.1. Tim Timothy H. Keitt wrote: > Hi, > > It appears that limit and offset do not work in a subselect such as: > > update my_table set my_col = new_val where oid = (select oid from > my_table offset row_number limit 1); > > Basically, I need to

[HACKERS] offset and limit in update and subselect

2001-02-24 Thread Timothy H. Keitt
Hi, It appears that limit and offset do not work in a subselect such as: update my_table set my_col = new_val where oid = (select oid from my_table offset row_number limit 1); Basically, I need to update rows by offset from the beginning of the table. Even nicer would be upd

[HACKERS] pg_atoi() behavior change? Intentional?

2001-02-24 Thread Adam Haberlach
I've just upgraded to the beta4 in order to fix an RI deadlock we seemed to be having with 7.0.3 -- and it seems that one of the engineers has been writing some queries that cast a text field to an int and take advantage of the fact that we used to turn text fields with no digits into 0, m

Re: [HACKERS] Re: PostgreSQL JDBC

2001-02-24 Thread Peter Mount
At 13:05 23/02/01 -0500, Jeff Duffy wrote: >On Fri, 23 Feb 2001, Andy Engdahl wrote: > > > I seem to be having some problems w/ the psql jdbc driver. I'm able to > load the driver, but as soon as I try to connect w/ the database. here's > my code: > > > > import java.sql.*; > > > > public class

[HACKERS] pgaccess Japanese input capability patch

2001-02-24 Thread Tatsuo Ishii
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 transparent to tcl application programs, libraries are

Re: [HACKERS] WAL does not recover gracefully from out-of-disk-space

2001-02-24 Thread Hiroshi Inoue
Tom Lane wrote: > > With current sources: > > DEBUG: copy: line 629980, XLogWrite: new log file created - try to increase >WAL_FILES > DEBUG: copy: line 694890, XLogWrite: new log file created - try to increase >WAL_FILES > FATAL 2: copy: line 759383, ZeroFill(logfile 0 seg 13) failed: No sp