pg.ddx.io pgsql-sql@postgresql.org mailing list archive
help / color / mirror / Atom feedSame question about PostgreSql
6+ messages / 5 participants
[nested] [flat]
* Same question about PostgreSql
@ 2001-04-14 13:01 Sergey E. Volkov <sve@raiden.bancorp.ru>
0 siblings, 2 replies; 6+ messages in thread
From: Sergey E. Volkov @ 2001-04-14 13:01 UTC (permalink / raw)
To: pgsql-sql
Hi group,
We have a DSS system based on Informix IDS and number of OLTP systems based
on Interbase.
After we was running this system, we had have a unceasing serious problems
with Interbase.
1) Massive inserts, updates, deletes is crashed database internal structure
!!!.
we have to make backup and restore every night ( backup and restore for 1G
database is spent about 3 hours !!).
2) Garbage collection is crashed database internal structure !!!!!!!!!!
3) Backup sometimes can't process crashed database.
4) Restore frequently ( 50% of cases ) can't help ( because backup is not
valid even if backup utility is finished without errors ( constraints
violation and etc. ) !!!!)
OLTP database has about 300 tables and 250 store procedures.
Number of client connections 100 and less.
Maximum database size is about 1.5 G - 3 G.
Data from the OLTP systems periodically come into DSS database.
Excuse me for long entering. Finally questions.
How stable is PostgreSql ?
I know, PostgreSql doesn't support 'prepare ' operation, is it successful to
use one for OLTP databases ?
Thanks for responds.
Good luck.
Sergey.
^ permalink raw reply [nested|flat] 6+ messages in thread
* Re: Same question about PostgreSql
@ 2001-04-15 06:01 Poet/Joshua Drake <poet@linuxports.com>
parent: Sergey E. Volkov <sve@raiden.bancorp.ru>
1 sibling, 0 replies; 6+ messages in thread
From: Poet/Joshua Drake @ 2001-04-15 06:01 UTC (permalink / raw)
To: Sergey E. Volkov <sve@raiden.bancorp.ru>; +Cc: pgsql-sql
>How stable is PostgreSql ?
>I know, PostgreSql doesn't support 'prepare ' operation, is it successful to
>use one for OLTP databases ?
Speaking from experience, I have personally stress tested Postgres under
loads of over 512 persistent connections with our LXP application server
with zero problems.
J
>
>
>Thanks for responds.
>
>Good luck.
>
>Sergey.
>
>
>
>
>
>
>
>---------------------------(end of broadcast)---------------------------
>TIP 6: Have you searched our list archives?
>
>http://www.postgresql.org/search.mpl
>
--
--
<COMPANY>CommandPrompt - http://www.commandprompt.com </COMPANY>
<PROJECT>OpenDocs, LLC. - http://www.opendocs.org </PROJECT>
<PROJECT>LinuxPorts - http://www.linuxports.com </PROJECT>
<WEBMASTER>LDP - http://www.linuxdoc.org </WEBMASTER>
--
Instead of asking why a piece of software is using "1970s technology,"
start asking why software is ignoring 30 years of accumulated wisdom.
--
^ permalink raw reply [nested|flat] 6+ messages in thread
* Re: Same question about PostgreSql
@ 2001-04-15 22:27 Josh Berkus <josh@agliodbs.com>
parent: Sergey E. Volkov <sve@raiden.bancorp.ru>
1 sibling, 2 replies; 6+ messages in thread
From: Josh Berkus @ 2001-04-15 22:27 UTC (permalink / raw)
To: Sergey E. Volkov <sve@raiden.bancorp.ru>; pgsql-sql
Sergey,
> How stable is PostgreSql ?
More than Interbase :-) More than MS SQL Server. Maybe less than
Oracle or MySQL; it's open to debate.
Futher, because everything in Postgresql is "open" -- source code, data
files, system tables -- in the event of hardware or platform failure you
can always retrieve your data with text and file editors.
You may have trouble porting one thing, though ... at this time,
PostgreSQL does not support full stored procedures. While the custom
function feature can fulfill many stored procedure purposes, you will
not be able to port your procedures over directly.
Full stored procedures are planned for Postgres, but not for a couple of
versions.
-Josh Berkus
______AGLIO DATABASE SOLUTIONS___________________________
Josh Berkus
Complete information technology josh@agliodbs.com
and data management solutions (415) 565-7293
for law firms, small businesses fax 621-2533
and non-profit organizations. San Francisco
^ permalink raw reply [nested|flat] 6+ messages in thread
* Re: Same question about PostgreSql
@ 2001-04-16 11:12 Johannes Grødem <johs@copyleft.no>
parent: Josh Berkus <josh@agliodbs.com>
1 sibling, 0 replies; 6+ messages in thread
From: Johannes Grødem @ 2001-04-16 11:12 UTC (permalink / raw)
To: pgsql-sql; +Cc: Sergey E. Volkov <sve@raiden.bancorp.ru>; pgsql-sql
> More than Interbase :-) More than MS SQL Server. Maybe less than
> Oracle or MySQL; it's open to debate.
Um. In my experience, PostgreSQL is more stable than MySQL. MySQL dies
on me all the time, but I've never had it happen with PostgreSQL. (7.0.3,
currently.)
--
johs
^ permalink raw reply [nested|flat] 6+ messages in thread
* Re: Same question about PostgreSql
@ 2001-04-17 22:25 Nils Zonneveld <nils@mbit.nl>
parent: Josh Berkus <josh@agliodbs.com>
1 sibling, 1 reply; 6+ messages in thread
From: Nils Zonneveld @ 2001-04-17 22:25 UTC (permalink / raw)
To: pgsql-sql
Josh Berkus wrote:
> Full stored procedures are planned for Postgres, but not for a couple of
> versions.
>
I always thought that Pl/PgSQL functions where 'stored procedures'.
Probably I'm wrong, but whats the difference between a Pl/PgSQL function
and a stored procedure? (just curious).
Regards,
Nils Zonneveld
^ permalink raw reply [nested|flat] 6+ messages in thread
* Re: Re: Same question about PostgreSql
@ 2001-04-18 04:24 Josh Berkus <josh@agliodbs.com>
parent: Nils Zonneveld <nils@mbit.nl>
0 siblings, 0 replies; 6+ messages in thread
From: Josh Berkus @ 2001-04-18 04:24 UTC (permalink / raw)
To: Nils Zonneveld <nils@mbit.nl>; pgsql-sql
Nils,
> I always thought that Pl/PgSQL functions where 'stored procedures'.
> Probably I'm wrong, but whats the difference between a Pl/PgSQL
> function
> and a stored procedure? (just curious).
Postgres functions have really expanded the concept of function, to the
point of *almost* being stored procedures. However, there are still a
few things missing:
1. Stored procedures must be able to return a rowset, possibly mutiple
rowsets.
2. Stored procedures usually accept an indefinite number of parameters.
3. Stored procedures should be capable of logging their activites.
4. Stored procedures should have access to the full range of DB control
language, includign cursors, transactions, and error handling.
Of the 4. I'm only certain that 1. is part of the SQL92 spec. Any more
authoritative opinions?
-Josh
______AGLIO DATABASE SOLUTIONS___________________________
Josh Berkus
Complete information technology josh@agliodbs.com
and data management solutions (415) 565-7293
for law firms, small businesses fax 621-2533
and non-profit organizations. San Francisco
^ permalink raw reply [nested|flat] 6+ messages in thread
end of thread, other threads:[~2001-04-18 04:24 UTC | newest]
Thread overview: 6+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2001-04-14 13:01 Same question about PostgreSql Sergey E. Volkov <sve@raiden.bancorp.ru>
2001-04-15 06:01 ` Poet/Joshua Drake <poet@linuxports.com>
2001-04-15 22:27 ` Josh Berkus <josh@agliodbs.com>
2001-04-16 11:12 ` Johannes Grødem <johs@copyleft.no>
2001-04-17 22:25 ` Nils Zonneveld <nils@mbit.nl>
2001-04-18 04:24 ` Josh Berkus <josh@agliodbs.com>
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox