I've been working to make PostgreSQL run on SunOS4 (again).
I have committed massive changes for SunOS4 port. Tested on:
SunOS 4.1.4
Vine Linux 2.1 (variant of RedHat Linux 6.2J)
FreeBSD 4.2-RELEASE
Please let me know if I have broken something.
--
Tatsuo Ishii
On Mon, 26 Feb 2001 22:16:35 -0500 Tom Lane [EMAIL PROTECTED] wrote:
Jaume Teixi [EMAIL PROTECTED] writes:
I finally percated that when data contains '' or '' it's impossible
to
parse trought:
COPY products FROM '/var/lib/postgres/dadesi.txt' USING DELIMITERS '|'
\g
it causes:
Bruce Momjian [EMAIL PROTECTED] writes:
If you like I'll post the patch, but it strikes me as a waste of list
bandwidth --- anyone who is likely to actually review it is perfectly
capable of doing cvs diff for themselves ...
Posting patch is only useful if you want people to review it.
I agree that 30k looks like the magic delay, and probably 30/5 would be a
good conservative choice. But now I think about the choice of number, I
think it must vary with the speed of the machine and length of the
transactions; at 20tps, each TX is completing in around 50ms.
I think disk
At 10:56 27/02/01 +0100, Zeugswetter Andreas SB wrote:
I agree that 30k looks like the magic delay, and probably 30/5 would be a
good conservative choice. But now I think about the choice of number, I
think it must vary with the speed of the machine and length of the
transactions; at
Hi,
I have an application which has an queue of data it has to insert into
a table in a local database. the insert-queries syntax is all the same,
and the values are the only thing that differs. The insert-query looks
like this:
INSERT INTO "table" VALUES(a, b, c, d, e, f, g, h)
...but I
On Tue, 27 Feb 2001, Xu Yifeng wrote:
Hello Tom,
Tuesday, February 27, 2001, 12:45:18 PM, you wrote:
TL Bruce Momjian [EMAIL PROTECTED] writes:
I know it is easy for you, but the number of reports and problems we
hear about shows it is an issue for some.
TL We hear some reports, but
So 7.0.3 is twice as fast only with fsync off.
Are there FK updates/deletes in pgbench' tests?
Remember how SELECT FOR UPDATE in FK triggers
affects performance...
Also, 5 clients is small number.
Vadim
P.S. Sorry for delays with my replies -
internet connection is pain here: it takes
5-10
Regardless of whether this particular behavior is fixable,
this brings up something that I think we *must* do before
7.1 release: create a utility that blows away a corrupted
logfile to allow the system to restart with whatever is in
the datafiles. Otherwise, there is no recovery technique
The Hermit Hacker wrote:
Morning all ...
Are there any major outstandings that ppl have on their plates,
that should prevent a release? I'd like to put out an RC1 by Friday this
week, with a full release schedualed for March 15th ... this would give
Thomas his two weeks for the
On Tue, 27 Feb 2001, you wrote:
Hi,
I have an application which has an queue of data it has to insert into
a table in a local database. the insert-queries syntax is all the same,
and the values are the only thing that differs. The insert-query looks
like this:
INSERT INTO "table"
I don't know about other 'commercial OSs', but I'd be shocked if a Linux
admin never does any kernel config cleanup befor egoing production *shrug*
oops...
- Thomas
Tatsuo Ishii writes:
I've been working to make PostgreSQL run on SunOS4 (again).
I have committed massive changes for SunOS4 port. Tested on:
SunOS 4.1.4
Vine Linux 2.1 (variant of RedHat Linux 6.2J)
FreeBSD 4.2-RELEASE
Please let me know if I have broken something.
I think the
Tatsuo Ishii [EMAIL PROTECTED] writes:
Tom, do you have a plan to make a back patch for 7.0.3?
No, I don't. No time for it now.
I got a bug report from a user with a script to reproduce the
problem. Seems the backend consumes infinite memory.
Not infinite, surely ;-) ... but possibly more
Steffen Emil Thorkildsen [EMAIL PROTECTED] writes:
I have an application which has an queue of data it has to insert into
a table in a local database. the insert-queries syntax is all the same,
and the values are the only thing that differs. The insert-query looks
like this:
INSERT INTO
Marko Kreen writes:
test/bench/{create|runtest}.sh uses switch '-Q' for
postgres, but postgres gives error on it. Otherwise
seems working, only lots of debug output is seen.
Replace it with '-d 0'. I'm not sure these benchmark tools are maintained
at all. contrib/pgbench seems to be
Steffen Emil Thorkildsen [EMAIL PROTECTED] writes:
me. Are there ways to precompile a sqlquery or do other tricks to get the
*fastest* insertion-rate, since the data-queue is growing faster than
200/sec... I don't care about integrity etc!
I'm using PostgreSQL 7.0.3, RH 6.2 Linux 2.2.4,
The Hermit Hacker writes:
I don't ... I personally admin FreeBSD and Solaris boxen ... FreeBSD,
first step is to always recompile the kernel after an install, to get rid
of crud and add Shared Memory ... the Solaris boxes, you add a couple of
lines to /etc/system and reboot, and you have
Tom Lane wrote:
Jaume Teixi [EMAIL PROTECTED] writes:
I finally percated that when data contains '' or '' it's impossible to
parse trought:
COPY products FROM '/var/lib/postgres/dadesi.txt' USING DELIMITERS '|' \g
it causes:
SELECT edicion FROM products;
edicion
"Oliver Elphick" [EMAIL PROTECTED] writes:
I think this happens when the front-end encoding is SQL_ASCII and the
database is using UNICODE. Then, there are misunderstandings between
front-end and back-end, so that a single character with the eighth bit
set may be sent by the front-end and
(...)
I don't care about integrity etc!
You should !-)
You can find some valueable tips in the documentation:
http://www.de.postgresql.org/users-lounge/docs/7.0/user/c4929.htm
In the docs there is this paragraph:
Disable Auto-commit
Turn off auto-commit and just do one commit at the
Tatsuo Ishii [EMAIL PROTECTED] writes:
I have committed massive changes for SunOS4 port. Tested on:
SunOS 4.1.4
Vine Linux 2.1 (variant of RedHat Linux 6.2J)
FreeBSD 4.2-RELEASE
Please let me know if I have broken something.
Everything still builds and passes regression on HPUX, but I
Hi all,
I've been trying to play with beta5 today on unixware 711. I have 2
problems:
1) enabling --with-tcl yields to link errors on bin/pgtclsh and
interfaces/pl/tcl because Makefile insists on linking with libtcl7.6.0
instead on libtcl7.6
2) enabling --with-openssl causes a compilation
Emmanuel Charpentier [EMAIL PROTECTED] writes:
Yep ! As of beta4, the ODBC driver is still seriously broken (the
original libpsqlodbc.so.0.26 doesn't even connect. A version patched by
Nick Gorham allows some connectivity (you can query the DB), but still
has some serious breakage (i. e. no
Vince Vielhaber writes:
is regression.out and/or regression.diff deleted if the tests pass? I've
never seen all tests pass so I don't know but I just had someone tell me
that it does.
We've come to a point where all tests should pass all the time on all
supported platforms. If they don't,
On Tue, 27 Feb 2001, Peter Eisentraut wrote:
Vince Vielhaber writes:
is regression.out and/or regression.diff deleted if the tests pass? I've
never seen all tests pass so I don't know but I just had someone tell me
that it does.
We've come to a point where all tests should pass all
* Olivier PRENANT [EMAIL PROTECTED] [010227 13:30]:
Hi all,
I've been trying to play with beta5 today on unixware 711. I have 2
problems:
1) enabling --with-tcl yields to link errors on bin/pgtclsh and
interfaces/pl/tcl because Makefile insists on linking with libtcl7.6.0
instead on
Vince Vielhaber writes:
It was a snapshot - no idea what kind of shape it was in and I don't
recall how I did the check, but it may have been installcheck.
Even snapshots should work all the time. If not, it should be reported,
not posted to a web page.
Either way my question still needs
On Tue, 27 Feb 2001, Vince Vielhaber wrote:
On Tue, 27 Feb 2001, Peter Eisentraut wrote:
Vince Vielhaber writes:
is regression.out and/or regression.diff deleted if the tests pass? I've
never seen all tests pass so I don't know but I just had someone tell me
that it does.
On Tue, 27 Feb 2001, Larry Rosenman wrote:
* Olivier PRENANT [EMAIL PROTECTED] [010227 13:30]:
Hi all,
I've been trying to play with beta5 today on unixware 711. I have 2
problems:
1) enabling --with-tcl yields to link errors on bin/pgtclsh and
interfaces/pl/tcl because
* Olivier PRENANT [EMAIL PROTECTED] [010227 15:00]:
On Tue, 27 Feb 2001, Larry Rosenman wrote:
* Olivier PRENANT [EMAIL PROTECTED] [010227 13:30]:
Hi all,
I've been trying to play with beta5 today on unixware 711. I have 2
problems:
1) enabling --with-tcl yields to link
I have completed a database internals presentation. The PDF is at:
http://candle.pha.pa.us/main/writings/internals.pdf
I am interested in any comments. I need to add text to it. FYI, you
will find a system catalog chart in the presentation.
--
Bruce Momjian
Peter Eisentraut [EMAIL PROTECTED] writes:
Either way my question still needs to be answered. If there are no
errors, is regression.out and regression.diff deleted? I can see the
diff file being empty, but deleted?
The diff file always exists; if all tests passed, it's empty.
Forgot your
Vince Vielhaber [EMAIL PROTECTED] writes:
The test output should come from 'gmake check', not the test against an
already installed server ('installcheck').
It was a snapshot - no idea what kind of shape it was in and I don't
recall how I did the check, but it may have been installcheck.
Matthew Kirkwood [EMAIL PROTECTED] writes:
I had assumed that the overhead would come from synchronous
metadata incurring writes of at least the inode, block bitmap
and probably an indirect block for each syscall.
No Unix that I've ever heard of forces metadata to disk after each
"write"
On Sat, 24 Feb 2001, Tom Lane 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 first allocating and zeroing (and hence
dirtying) 16Mb of memory.
Uh, the existing code does not
Tom Lane wrote:
Emmanuel Charpentier [EMAIL PROTECTED] writes:
Yep ! As of beta4, the ODBC driver is still seriously broken (the
original libpsqlodbc.so.0.26 doesn't even connect. A version patched by
Nick Gorham allows some connectivity (you can query the DB), but still
has some
"Oliver Elphick" [EMAIL PROTECTED] writes:
I think this happens when the front-end encoding is SQL_ASCII and the
database is using UNICODE. Then, there are misunderstandings between
front-end and back-end, so that a single character with the eighth bit
set may be sent by the front-end
Attached is a single INSERT that shows the problem. The character after the
word "Fiber" truncates the text when using JDBC. NOTE, the text IS in the
database, that is, the dump/restore seems ok, the problem is when trying to
read the text later. The database is UTF8 and I just tested with
Attached is a single INSERT that shows the problem. The character after the
word "Fiber" truncates the text when using JDBC. NOTE, the text IS in the
database, that is, the dump/restore seems ok, the problem is when trying to
read the text later. The database is UTF8 and I just tested with
Are there any major outstandings that ppl have on their plates,
that should prevent a release? I'd like to put out an RC1 by Friday this
week, with a full release schedualed for March 15th ... this would give
Thomas his two weeks for the docs freeze ...
I'm interested to know what
Mario Weilguni wrote:
(...)
I don't care about integrity etc!
You should !-)
You can find some valueable tips in the documentation:
http://www.de.postgresql.org/users-lounge/docs/7.0/user/c4929.htm
In the docs there is this paragraph:
Disable Auto-commit
Turn off
I have a copy of OpenOffice for LinuxPPC but have not figured out how to
tell it to connect to Postgres. If someone can slip me a clue on how to
configure it and do simple database stuff with it, I'll try to clean up
the most pressing ODBC problems before we release.
I've got a clue for
Any suggestion why postmaster/postgres would think it had been compiled
with BLCKSZ 0? :
root@blue:/usr/local/pgsql# su postgres -c "bin/postmaster -D
/usr/local/pgsql/data "
DEBUG: Data Base System is starting up at Tue Feb 27 22:31:51 2001
FATAL 2: database was initialized with BLCKSZ 0,
Thomas Lockhart [EMAIL PROTECTED] writes:
I'm interested to know what exactly takes two weeks with the docs and what
could be done to speed it up.
The "official" version of the story is that it takes ~10-20 hours for me
to work through the docs to format them for hardcopy with ApplixWare,
"Dominic J. Eidson" [EMAIL PROTECTED] writes:
Any suggestion why postmaster/postgres would think it had been compiled
with BLCKSZ 0? :
root@blue:/usr/local/pgsql# su postgres -c "bin/postmaster -D
/usr/local/pgsql/data "
DEBUG: Data Base System is starting up at Tue Feb 27 22:31:51 2001
Thomas Lockhart wrote:
I have a copy of OpenOffice for LinuxPPC but have not figured out how to
tell it to connect to Postgres. If someone can slip me a clue on how to
configure it and do simple database stuff with it, I'll try to clean up
the most pressing ODBC problems before we
I've got a clue for ApplixWare, if you happen to have that package
(US$90).
Please post it, Thomas.
I got nowhere following their instructions.
Uh, who's instructions? We have a writeup on Applix and ODBC in the
docs. Have you found those, or are those falling short of helpful?
48 matches
Mail list logo
