[HACKERS] docs Japanese translation

Hi, We (SRA) have done the translation of PostgreSQL 7.1 docs into Japanese. They can be freely available at http://osb.sra.co.jp/PostgreSQL/Manual/. -- Tatsuo Ishii ---(end of broadcast)--- TIP 1: subscribe and unsubscribe commands go to [EMAIL PR

Re: [HACKERS] Re: Encrypting pg_shadow passwords

> On Tue, Jun 26, 2001 at 11:02:15AM -0400, Bruce Momjian wrote: > > This is the first time I am hearing people are more concerned about > > pg_shadow security than the wire security. I can see cases where people > > are on secure networks or are using only local users where having > > pg_shadow

Re: [HACKERS] Re: Encrypting pg_shadow passwords

On Tue, Jun 26, 2001 at 11:02:15AM -0400, Bruce Momjian wrote: > This is the first time I am hearing people are more concerned about > pg_shadow security than the wire security. I can see cases where people > are on secure networks or are using only local users where having > pg_shadow encrypted

[HACKERS] libpq autoconf scripts?

Anyone maintaining generic autoconf scripts for linking against libpq, i.e., returns path to libpq-fe.h and proper link options? Tim -- Timothy H. Keitt Department of Ecology and Evolution State University of New York at Stony Brook Stony Brook, New York 11794 USA Phone: 631-632-1101, FAX: 631

Re: [HACKERS] timestamp with/without time zone

> Is this a TODO item? Sure, but I'd hate to have all of these individual items showing up as separate things in some ToDo list, since it won't paint a coherent picture of where things are headed. I'm planning on doing some work on timestamp, which will include: o support for "ISO variants" on

Re: [HACKERS] Postgresql bulk fast loader

> Does postgresql have any sort of fast bulk loader? COPY command. -- Bruce Momjian| http://candle.pha.pa.us [EMAIL PROTECTED] | (610) 853-3000 + If your life is a hard drive, | 830 Blythe Avenue + Christ can be your backup.| Drexe

[HACKERS] Re: SOMAXCONN (was Re: Solaris source code)

Tom Lane <[EMAIL PROTECTED]> writes: > [EMAIL PROTECTED] (Nathan Myers) writes: > > If you want to make it more complicated, it would be more useful to > > be able to set the value lower for runtime environments where PG is > > competing for OS resources with another daemon that deserves higher

[HACKERS] Re: [GENERAL] 2 gig file size limit

> (This question was answered several days ago on this list; please check > the list archives before posting. I believe it's also in the FAQ.) > > > If PostgreSQL is run on a system that has a file size limit (2 > > gig?), where might cause us to hit the limit? > > Postgres will never internal

Re: SOMAXCONN (was Re: [HACKERS] Solaris source code)

> [EMAIL PROTECTED] (Nathan Myers) writes: > > All the OSes we know of fold it to 128, currently. We can jump it > > to 10240 now, or later when there are 20GHz CPUs. > > > If you want to make it more complicated, it would be more useful to > > be able to set the value lower for runtime enviro

Re: [HACKERS] i need help for JDBC

>I have compiled with --with-multibytes, >but the JDBC really can not recognize chinese character. > >Any suggestion is kind for me. Hard to tell unless provided PostgreSQL version given and what kind of encoding you use. > [×ã²»³ö»§ ÇáËÉÉÏÍø] ÉÏÍøרÓúţº95963£¬Óû§Ãû/ÃÜÂ룺263 Do

Re: SOMAXCONN (was Re: [HACKERS] Solaris source code)

On Tue, Jul 10, 2001 at 06:36:21PM -0400, Tom Lane wrote: > [EMAIL PROTECTED] (Nathan Myers) writes: > > All the OSes we know of fold it to 128, currently. We can jump it > > to 10240 now, or later when there are 20GHz CPUs. > > > If you want to make it more complicated, it would be more useful

[HACKERS] Re: Postgresql bulk fast loader

Naomi Walker wrote: > > Does postgresql have any sort of fast bulk loader? It has a very cool SQL extension called COPY. Super fast. Command: COPY Description: Copies data between files and tables Syntax: COPY [ BINARY ] table [ WITH OIDS ] FROM { 'filename' | stdin } [ [USING] DELI

[HACKERS] Postgresql bulk fast loader

Does postgresql have any sort of fast bulk loader? -- Naomi Walker Chief Information Officer Eldorado Computing, Inc. 602-604-3100 ext 242 ---(end of broadcast)--- TIP 2: you can get off all lists at once with the unregister command (send "un

Re: [HACKERS] grant and SQL92

Bruce Momjian <[EMAIL PROTECTED]> writes: > I do have a pending patch from him that arrived > today that deals with the CREATEDB/CREATEUSER ordering. I have not > applied it because it hasn't appeared on patches yet for people to > comment. I already applied his CREATE/ALTER USER patch, because

Re: [HACKERS] Re: Time to read pg_hba.conf (Re: [PATCHES] [PATCH] Patchto make...)

> Peter Eisentraut <[EMAIL PROTECTED]> writes: > > So we're looking at a possible 12% win. > > Many thanks for doing this legwork. > > The possible win from not having to read the file at all is probably > somewhat higher than that, but not vastly higher. Accordingly, I'd > say that pre-parsing

Re: SOMAXCONN (was Re: [HACKERS] Solaris source code)

[EMAIL PROTECTED] (Nathan Myers) writes: > All the OSes we know of fold it to 128, currently. We can jump it > to 10240 now, or later when there are 20GHz CPUs. > If you want to make it more complicated, it would be more useful to > be able to set the value lower for runtime environments where

Re: [HACKERS] varchar vs. text

Rachit Siamwalla <[EMAIL PROTECTED]> writes: > Is there any good reason to use VARCHAR over TEXT for a string field? The only reason to use VARCHAR is if you *want* the data to be truncated at a specific length. If you don't have a well-defined upper limit in mind, I'd recommend TEXT.

Re: [HACKERS] Re: [OT] Any major users of postgresql?

"John Moore" <[EMAIL PROTECTED]> writes: > In the case of PostgreSQL, as far as I can tell, one could lose all data > since the previous dump if one lost the database media. In Oracle or > Informix, that is *not* true, because they can do a point-in-time restore > from the last full save, based on

Re: [HACKERS] Any tips for this particular performance problem?

On Tue, Jul 10, 2001 at 09:46:07AM -0700, Stephan Szabo wrote: > On Tue, 10 Jul 2001, Sergio Bruder wrote: > > > If you have time, take a quick look at > > > > http://acidlab.sourceforge.net/perf/acid_perf.html > > > > PostgreSQL has serious scalability problems with snort + acid. Any > > advic

Re: [HACKERS] timestamp with/without time zone

> > I already commented what I thought about this: the current type is not > > either of the SQL-compatible timestamp types, and if we want to support > > the SQL-compatible semantics then we need three types, not two. > > Right, that was clear even to me ;) > > We were on that path for quite so

Re: AW: [HACKERS] pg_index.indislossy

[EMAIL PROTECTED] (Nathan Myers) writes: > Seriously, "indislossy" is a singularly poor name for a predicate. Perhaps, but it fits with the existing naming conventions for Postgres catalog columns. Unless we want to indulge in wholesale renaming of the system's catalog columns (and break an awfu

Re: [HACKERS] Strange query execution time

What does explain show for the two queries? On Wed, 4 Jul 2001, Michel Soto wrote: > Hi, > > Can someone explain why the following query takes 1 second when using > LIKE and takes 30 seconds when replacing LIKE by = in the WHERE ? > - instance_Attribute has 45 rows and Influence has 5 rows

Re: [HACKERS] way to pass NEW into function

What I did in a similar trigger was set a variable (of type RECORD) to NEW and then use that. (I actually used the appropriate fields, but record should... work) LER >> Original Message << On 7/10/01, 4:22:34 PM, Mike Cianflone <[EMAIL PROTECTED]> wrote rega

Re: [HACKERS] grant and SQL92

On Tue, 10 Jul 2001, Bruce Momjian wrote: > > > > > > Added to TODO: > > > > > > > > > > > > * Allow GRANT/REVOKE to handle multiple user/group names > > > > > > > > > > You must have missed the part about tomorrow. > > > > > > > > Did you already commit? I was watching for it but could very

Re: [HACKERS] grant and SQL92

> > > > > Added to TODO: > > > > > > > > > > * Allow GRANT/REVOKE to handle multiple user/group names > > > > > > > > You must have missed the part about tomorrow. > > > > > > Did you already commit? I was watching for it but could very well > > > have missed it. > > > > I don't see it. Th

[HACKERS] i need help for JDBC

Hi, I have compiled with --with-multibytes, but the JDBC really can not recognize chinese character. Any suggestion is kind for me. malix shanghai china _ [×ã²»³ö»§ ÇáËÉÉÏÍø] ÉÏÍøרÓúţº95963£¬Óû§Ãû/ÃÜÂ룺263 »¯×±Æ·ÏÄÈÕÌػݣ¬½µ¼Û¿ñ³

Re: SOMAXCONN (was Re: [HACKERS] Solaris source code)

> Bruce Momjian <[EMAIL PROTECTED]> writes: > > Could we test SOMAXCONN and set PG_SOMAXCONN to 1000 only if SOMAXCONN1 > > is less than 1000? > > Why bother? > > If you've got some plausible scenario where 1000 is too small, we could > just as easily make it 1. I don't see the need for yet

[HACKERS] Re: [OT] Any major users of postgresql?

> It probably depends on what you call "serious". Anyway, the project I am > working on is a online community for alternate investments and is built > around a PostgreSQL (first 7.0, now 7.1) database: it's > but unfortunately most of it is limited > only to subscribe

[HACKERS] varchar vs. text

Is there any good reason to use VARCHAR over TEXT for a string field? ie. performance hits, etc. Other than running into the row size limit problem, are there any large storage / performance penalties of using TEXT for virtually all strings? For ex. A phone number. This field probably wouldn't

Re: [HACKERS] JDBC Support - prepared Statements?

> > yes I did so. The name of the rpm I recently downloaded is: > > postgresql-jdbc-7.1.2-4PGDG.i386.rpm and it is throwing the exception when > > calling the prepareStatement() Method. > > Hm, I build everything from source. Perhaps the RPM is buggy. I would get the JAR from: http:/

RE: [HACKERS] New SQL Datatype RECURRINGCHAR

The only problem with 'enum' is that all of the possible values must be specified at CREATE time. A logical extension to this would be to allow for 'dynamic extensions' to the list. -Original Message- From: Tom Lane [mailto:[EMAIL PROTECTED]] Sent: Tuesday, July 03, 2001 4:49 PM To: Rod

Re: [HACKERS] JDBC Support - prepared Statements?

> ... and the only problem we are facing is the I get an exception stating that > with the current jdbc driver prepared statements are not supported (yet). Did you try the latest 7.1.2 release? I did so recently and did not encounter any problems with PreparedStatements. (There are still other b

[HACKERS] Re: Time to read pg_hba.conf (Re: [PATCHES] [PATCH] Patch to make...)

Peter Eisentraut <[EMAIL PROTECTED]> writes: > So we're looking at a possible 12% win. Many thanks for doing this legwork. The possible win from not having to read the file at all is probably somewhat higher than that, but not vastly higher. Accordingly, I'd say that pre-parsing the file is not

Re: [HACKERS] grant and SQL92

On Tue, 10 Jul 2001, Bruce Momjian wrote: > > On Mon, 9 Jul 2001, Peter Eisentraut wrote: > > > > > Bruce Momjian writes: > > > > > > > > On Sat, 9 Jun 2001, Peter Eisentraut wrote: > > > > > > > > > > > Vince Vielhaber writes: > > > > > > > > > > > > > I can grant a series of privileges (comma s

Re: SOMAXCONN (was Re: [HACKERS] Solaris source code)

Bruce Momjian <[EMAIL PROTECTED]> writes: > I was thinking: > #if SOMAXCONN >= 1000 > #define PG_SOMAXCONN SOMAXCONN > #else > #define PG_SOMAXCONN 1000 > #endif Not in config.h, you don't. Unless you want (or whichever header defines SOMAXCONN; how consistent is

Re: SOMAXCONN (was Re: [HACKERS] Solaris source code)

Bruce Momjian <[EMAIL PROTECTED]> writes: > Could we test SOMAXCONN and set PG_SOMAXCONN to 1000 only if SOMAXCONN1 > is less than 1000? Why bother? If you've got some plausible scenario where 1000 is too small, we could just as easily make it 1. I don't see the need for yet another configu

RE: [HACKERS] New SQL Datatype RECURRINGCHAR

Alex, I think I fully understand your position. Let me put wrap up our conversation so far. Given the application requirements: 1) contacts have a type. 2) new types must be added on the fly as needed. 3) types names rarely change. 4) the number of contacts should scale to support m

Re: [HACKERS] timestamp with/without time zone

> > I believe everyone already agreed that 'current' should be removed. > > 'invalid' seems somewhat redundant with NULL, so I wouldn't object to > > taking it out; on the other hand, is it hurting anything? Also, it > > seems a bad idea to remove it from timestamp if we leave it in abstime; > >

Re: [HACKERS] Async PQgetResult() question.

Uh oops! I misread IIRC as (IRC, i.e. Internet Relay Chat or something similar.) It is too early! ;) I'll dig in the archives. Thanks, Matthew At 12:03 PM 7/8/2001 -0400, Matthew Hagerty wrote: >At 11:44 PM 7/7/2001 -0400, Tom Lane wrote: >>Matthew Hagerty <[EMAIL PROTECTED]> writes: >> > So

Re: [HACKERS] grant and SQL92

> On Mon, 9 Jul 2001, Peter Eisentraut wrote: > > > Bruce Momjian writes: > > > > > > On Sat, 9 Jun 2001, Peter Eisentraut wrote: > > > > > > > > > Vince Vielhaber writes: > > > > > > > > > > > I can grant a series of privileges (comma separated) on a series of > > > > > > objects (comma separate

[HACKERS] Re: Backups WAS: 2 gig file size limit

Lamar Owen wrote: > > On Friday 06 July 2001 18:51, Naomi Walker wrote: > > If PostgreSQL is run on a system that has a file size limit (2 gig?), where > > might cause us to hit the limit? > > Since PostgreSQL automatically segments its internal data files to get around > such limits, the only p

RE: [HACKERS] New SQL Datatype RECURRINGCHAR

> various disagreements and "quotes"... I agree that you disagree :) RECURRINGCHAR does not break normal form. It simply optimizes the storage of reference values (recurring keys). This allows for the use of 'long words' as reference values with a great deal of system storage savings and

RE: [HACKERS] New SQL Datatype RECURRINGCHAR

>> It's apparent that there is a lot of duplicate space used in the storage >> of this information. The idea is if order.status was stored as a >> RECURRINGCHAR >> then the only data stored for the row would be a reference to the value of >> the column. The actual values would be stored in a sepa

[HACKERS] SNMP support

Has anyone thought about adding SNMP support to PostgreSQL? RFC1697 contains the MIB file for RDBMSs. Has anyone worked with a RDBMS that supports SNMP and, if so, did they find it useful? I'm just learning about SNMP, but it seems that it has the potential to be useful. Thoughts? New to the l

Re: SOMAXCONN (was Re: [HACKERS] Solaris source code)

On Tue, Jul 10, 2001 at 05:06:28PM -0400, Bruce Momjian wrote: > > Mathijs Brands <[EMAIL PROTECTED]> writes: > > > OK, I tried using 1024 (and later 128) instead of SOMAXCONN (defined to > > > be 5 on Solaris) in src/backend/libpq/pqcomm.c and ran a few regression > > > tests on two different Spa

[HACKERS] Re: Production Backup and Recovery

"Doug McNaught" <[EMAIL PROTECTED]> wrote in message news:[EMAIL PROTECTED]... > "P. Dwayne Miller" <[EMAIL PROTECTED]> writes: > > > Is it documented somewhere how to do on-line backups and then how to > > recover from some event using those backups with no (or minimum) loss of > > data? > > Rig

[HACKERS] way to pass NEW into function

Is it possible to trick pg/sql to allow passing of the NEW record into a function? I've got a trigger that gets kicked off before an insert and I need to call another function and pass that record in, but doing a perform activate_event(NEW); /* my function is activate_event(OPAQUE) */ onl

Re: SOMAXCONN (was Re: [HACKERS] Solaris source code)

> Mathijs Brands <[EMAIL PROTECTED]> writes: > > OK, I tried using 1024 (and later 128) instead of SOMAXCONN (defined to > > be 5 on Solaris) in src/backend/libpq/pqcomm.c and ran a few regression > > tests on two different Sparc boxes (Solaris 7 and 8). The regression > > test still fails, but fo

Re: [HACKERS] JDBC Support - prepared Statements?

> yes I did so. The name of the rpm I recently downloaded is: > postgresql-jdbc-7.1.2-4PGDG.i386.rpm and it is throwing the exception when > calling the prepareStatement() Method. Hm, I build everything from source. Perhaps the RPM is buggy. -- Best regards Rainer Klute Dipl.-Inform.

[HACKERS] Strange query execution time

Hi, Can  someone explain why the following query takes  1 second when using LIKE and takes 30 seconds when replacing LIKE by = in the WHERE ? - instance_Attribute  has 45 rows and Influence has 5 rows. - Postgresql 7.1 Regards = SELECT E1A1.nameInstance AS inst

Re: [HACKERS] Buffer access rules, and a probable bug

Bill Studenmund <[EMAIL PROTECTED]> writes: > One problem though is that if you don't have a spin lock around the flag, > you can end up clearing it inadvertenty. i.e. two backends go to update > (different) bit flags. They each load the current value, and each set the > (different) bit they want

Re: [HACKERS] grant and SQL92

On Mon, 9 Jul 2001, Peter Eisentraut wrote: > Bruce Momjian writes: > > > > On Sat, 9 Jun 2001, Peter Eisentraut wrote: > > > > > > > Vince Vielhaber writes: > > > > > > > > > I can grant a series of privileges (comma separated) on a series of > > > > > objects (comma separated) to either a user,

Re: [HACKERS] Buffer access rules, and a probable bug

Sorry for the delay. On Tue, 3 Jul 2001, Tom Lane wrote: > [EMAIL PROTECTED] (Nathan Myers) writes: > > > Also, as hints, would it be Bad(tm) if an attempt to clear one failed? > > Clearing hint bits is also an exclusive-lock-only operation. Notice > I specified that *setting* them is the onl

Re: [HACKERS] grant and SQL92

Bruce Momjian writes: > > On Sat, 9 Jun 2001, Peter Eisentraut wrote: > > > > > Vince Vielhaber writes: > > > > > > > I can grant a series of privileges (comma separated) on a series of > > > > objects (comma separated) to either a user, group or public NOT a > > > > comma separated list of users

[HACKERS] Time to read pg_hba.conf (Re: [PATCHES] [PATCH] Patch to make...)

Tom Lane writes: > Since pg_hba.conf is re-read on every connection, I've always thought > it was pretty bogus to bulk it up with that much internal documentation. > I've not tried to measure how much time it takes the postmaster to skip > over those 200 comment lines, but it can't be completely

Re: AW: [HACKERS] pg_index.indislossy

On Tue, Jul 10, 2001 at 01:36:33PM -0400, Tom Lane wrote: > Peter Eisentraut <[EMAIL PROTECTED]> writes: > > But why is this called lossy? Shouldn't it be called "exceedy"? > > Good point ;-). "lossy" does sound like the index might "lose" tuples, > which is exactly what it's not allowed to do;

[HACKERS] selecting from cursor/function

I have 'select ... from cursor foo, tables ...' working, and halfway done with functions-as-result sets. A few questions to gurus: a) Currently, I have a shift-reduce conflict, because cursor is a valid TokenId. It can be resolved by removing it from list of TokenId, but if someone was naming on

SOMAXCONN (was Re: [HACKERS] Solaris source code)

Mathijs Brands <[EMAIL PROTECTED]> writes: > OK, I tried using 1024 (and later 128) instead of SOMAXCONN (defined to > be 5 on Solaris) in src/backend/libpq/pqcomm.c and ran a few regression > tests on two different Sparc boxes (Solaris 7 and 8). The regression > test still fails, but for a differ

Re: AW: [HACKERS] pg_index.indislossy

Peter Eisentraut <[EMAIL PROTECTED]> writes: > But why is this called lossy? Shouldn't it be called "exceedy"? Good point ;-). "lossy" does sound like the index might "lose" tuples, which is exactly what it's not allowed to do; it must find all the tuples that match the query. The terminology

Re: AW: [HACKERS] pg_index.indislossy

> Peter Eisentraut <[EMAIL PROTECTED]> writes: > > But why is this called lossy? Shouldn't it be called "exceedy"? > > Good point ;-). "lossy" does sound like the index might "lose" tuples, > which is exactly what it's not allowed to do; it must find all the > tuples that match the query. > >

Re: AW: AW: [HACKERS] pg_index.indislossy

> > > > > > > > > Can someone tell me what we use indislossy for? > > > > > > > > > > Ok, so the interpretation of this field is: > > > > > A match in the index needs to be reevaluated in the heap tuple data, > > > > > since a match in the index does not necessarily mean, that the hea

Re: [HACKERS] Any tips for this particular performance problem?

On Tue, 10 Jul 2001, Sergio Bruder wrote: > If you have time, take a quick look at > > http://acidlab.sourceforge.net/perf/acid_perf.html > > PostgreSQL has serious scalability problems with snort + acid. Any > advices? > > (Now I'm using MySQL with my SNORT/ACID setup, but I'm willing to > ch

[HACKERS] FE/BE protocol oddity

The description of the FE/BE protocol says: | The postmaster uses this info and the contents of the pg_hba.conf file | to determine what authentication method the frontend must use. The | postmaster then responds with one of the following messages: [...] | If the frontend does not support the aut

Re: AW: [HACKERS] pg_index.indislossy

Tom Lane writes: > Not true at all. The tuple commit status needs to be rechecked, yes, > but with a normal index it is not necessary to recheck whether the index > key field actually satisfies the index qual conditions. With a lossy > index it *is* necessary to recheck --- the index may return

Re: AW: [HACKERS] pg_index.indislossy

Peter Eisentraut <[EMAIL PROTECTED]> writes: > Bruce Momjian writes: > A match in the index needs to be reevaluated in the heap tuple data, > since a match in the index does not necessarily mean, that the heap tuple > matches. > AFAIK, this is true for all indexes in PostgreSQL, because index row

Re: AW: [HACKERS] pg_index.indislossy

> Bruce Momjian writes: > > > > > > > Can someone tell me what we use indislossy for? > > > > > > Ok, so the interpretation of this field is: > > > A match in the index needs to be reevaluated in the heap tuple data, > > > since a match in the index does not necessarily mean, that the heap tu

AW: AW: [HACKERS] pg_index.indislossy

> > > > > > > Can someone tell me what we use indislossy for? > > > > > > > > Ok, so the interpretation of this field is: > > > > A match in the index needs to be reevaluated in the heap tuple data, > > > > since a match in the index does not necessarily mean, that the heap >tupl

Re: AW: [HACKERS] pg_index.indislossy

Bruce Momjian writes: > > > > > Can someone tell me what we use indislossy for? > > > > Ok, so the interpretation of this field is: > > A match in the index needs to be reevaluated in the heap tuple data, > > since a match in the index does not necessarily mean, that the heap tuple > >

Re: [HACKERS] Any tips for this particular performance problem?

Hannu Krosing wrote: > Sergio Bruder wrote: > > > > If you have time, take a quick look at > > > > http://acidlab.sourceforge.net/perf/acid_perf.html > > > > PostgreSQL has serious scalability problems with snort + acid. Any > > advices? > > Usually porting from MySQL to PostgreSQL needs some rewr

Re: [HACKERS] Tips performance under solaris

Bruce Momjian <[EMAIL PROTECTED]> writes: > So it does I/O directly from the user buffer to disk, bypassing the > system cache. I am not sure if that is a good idea because you are not > using the system buffer cache nor is it allowing writes to be re-ordered > for optimial performance. ... and,

Re: AW: [HACKERS] Repost: Get table/field-identifiers in uppercase

Zeugswetter Andreas SB <[EMAIL PROTECTED]> writes: > I do not think the standard states what should happen when you start mixing > quoted and unquoted identifiers for the same object. Actually, it does: 13)A and a are equiva- lent if the of the (with every

Re: [HACKERS] Tips performance under solaris

> Hi, > > I try postgresql V 7.1.2 under solaris 2.8 ( patch + the last version ) and i use >directio implementation > for ufs . > Improved UFS Direct I/O Concurrency (Quick I/O Equivalent) > Solaris 8 1/01 update release allows concurrent read and write access to regular UFS >files. As datab

Re: [HACKERS] WaitOnLock: error on wakeup

Rachit Siamwalla <[EMAIL PROTECTED]> writes: > Anyone know why I could possibly get this error? This doesn't happen > deterministically. It wouldn't, because the problem arises from the interaction of multiple clients --- AFAIK it is not possible to get that error with only a single client, no ma

Re: [HACKERS] Any tips for this particular performance problem?

On Tue, Jul 10, 2001 at 04:04:43PM +0200, Hannu Krosing wrote: > Sergio Bruder wrote: > > > > If you have time, take a quick look at > > > > http://acidlab.sourceforge.net/perf/acid_perf.html > > > > PostgreSQL has serious scalability problems with snort + acid. Any > > advices? > > Usually po

Re: [HACKERS] Any tips for this particular performance problem?

Sergio Bruder wrote: > > If you have time, take a quick look at > > http://acidlab.sourceforge.net/perf/acid_perf.html > > PostgreSQL has serious scalability problems with snort + acid. Any > advices? Usually porting from MySQL to PostgreSQL needs some rewrite of queries and process logic if

[HACKERS] Tips performance under solaris

Hi, I try postgresql V 7.1.2 under solaris 2.8 ( patch + the last version ) and i use directio implementation for ufs . Improved UFS Direct I/O Concurrency (Quick I/O Equivalent) Solaris 8 1/01 update release allows concurrent read and write access to regular UFS files. As databases generally

[HACKERS] Any tips for this particular performance problem?

If you have time, take a quick look at http://acidlab.sourceforge.net/perf/acid_perf.html PostgreSQL has serious scalability problems with snort + acid. Any advices? (Now I'm using MySQL with my SNORT/ACID setup, but I'm willing to change to PostgreSQL if more tests are needed) Sergio Bruder

AW: [HACKERS] Repost: Get table/field-identifiers in uppercase

> When a new table or field is created without quotes, it is assumed to be > case-insensitive. Herefore I have some questions: > > - Is it SQL-92-conform to handle >"test"< like >test< without quotes, or > shouldn't it be >test< forced to lowercase? I do not understand this question. If you wan

Re: [HACKERS] Solaris source code

On Mon, Jul 09, 2001 at 02:03:16PM -0700, Nathan Myers allegedly wrote: > On Mon, Jul 09, 2001 at 02:24:17PM +0200, Mathijs Brands wrote: > > On Thu, Jul 05, 2001 at 02:03:31PM -0700, Naomi Walker allegedly wrote: > > > At 04:30 PM 7/5/01 -0400, Bruce Momjian wrote: > > > >I have purchased the Sol

[HACKERS] Quick Question!

Hi: A really simple question: I wanna set up some WAL related config parameter. I am wondering is it the same to add those parameter on postgresql.conf as to add them on /etc/rc.d/init.d/postgres.init?? ---(end of broadcast)--- TIP 5: Have you chec