Undeliverable Message - Mailing list pgsql-general
From | |
---|---|
Subject | Undeliverable Message |
Date | |
Msg-id | vines.n4,8+9dBGrA@SFRA0046. Whole thread Raw |
List | pgsql-general |
To: ISMTP@SFRA0046@Servers[<pgsql-general-digest@hub.org>] Cc: Subject: pgsql-general-digest V1 #325 Message not delivered to recipients below. Press F1 for help with VNM error codes. VNM3043: DE_VOLDER Fabrice@ATR_EXPL_LYON1@SFR_DO_CNTR_EST VNM3043 -- MAILBOX IS FULL The message cannot be delivered because the recipient's mailbox contains the maximum number of messages, as set by the system administrator. The recipient must delete some messages before any other messages can be delivered. The maximum message limit for a user's mailbox is 10,000. The default message limit is 1000 messages. Administrators can set message limits using the Mailbox Settings function available in the Manage User menu (MUSER). When a user's mailbox reaches the limit, the user must delete some of the messages before the mailbox can accept any more incoming messages. ---------------------- Original Message Follows ---------------------- pgsql-general-digest Sunday, May 23 1999 Volume 01 : Number 325 Index: Re: [GENERAL] PL/pgSQL - mailng list Re: [GENERAL] PL/pgSQL - mailng list To: pgsql-general@postgreSQL.org Compile problem on BSDi 3.0 Keyed Tables Re: [GENERAL] Keyed Tables Re: [GENERAL] Compile problem on BSDi 3.0 Re: [GENERAL] postgres getting slow Re: [GENERAL] Looking for Mr. Autonum RE: [GENERAL] For data based web site, which RDBMS is better & wh y ? RE: [GENERAL] Keyed Tables Re: [GENERAL] Keyed Tables Full Text Searches Re: [GENERAL] Full Text Searches ---------------------------------------------------------------------- Date: Sat, 22 May 1999 22:26:16 -0500 (CDT) From: Andy Lewis <alewis@themecca.net> Subject: Re: [GENERAL] PL/pgSQL - mailng list The only thing that I know is whats in the docs and whats in the src directory. I'd like to see/read more. I was going to pick up a Oracle book on it but, I'm afraid that PL/pgSQL and PL/SQL aren't the same. Thanks Andy On Sat, 22 May 1999, dustin sallings wrote: > On Sat, 22 May 1999, Andy Lewis wrote: > > How can we tell you more if we don't know what you know? It's > usually pretty safe to just go ahead and ask the question. You'll be > redirected if you've posted to the wrong place. > > // I'd just plain would like to know more about PL/pgSQL. > // > // Andy > // > // On Sat, 22 May 1999, Piotr Stelmaszyk wrote: > // > // > I'd like to get to know where should I post messages concerning > // > PL/pgSQL. > // > > // > > // > /--------------------------------------------------------/ > // > /- Piotr Stelmaszyk |---- Student of Computer Science ---/ > // > /------------------ | at Poznan University of Technology / > // > /----- mailto:kelman@fanthom.math.put.poznan.pl ---------/ > // > /----- mailto:kelman@alpha.net.pl -----------------------/ > // > /--------------------------------------------------------/ > // > > // > > // > > // > // > // > > -- > Principal Member Technical Staff, beyond.com The world is watching America, > pub 1024/3CAE01D5 1994/11/03 Dustin Sallings <dustin@spy.net> > | Key fingerprint > L______________________________________________ and America is watching TV. __ > ------------------------------ Date: Sat, 22 May 1999 21:05:22 -0700 (PDT) From: dustin sallings <dustin@spy.net> Subject: Re: [GENERAL] PL/pgSQL - mailng list On Sat, 22 May 1999, Andy Lewis wrote: It only took me about three clicks off of the home page to get this: http://postgresql.nextpath.com/docs/programmer/xplang.htm which does a pretty good job of describing it. I thought it did a good enough job at describing the installation and the language. Enough for me to get it going, anyway. I'm not sure how you could read anything more than the documentation (I mean, anything more should also be documentation). Have you tried it at all yet? Do you have any specific questions? Are there any things you're trying to do with it that you haven't been able to imagine or figure out yet? // The only thing that I know is whats in the docs and whats in the src // directory. I'd like to see/read more. I was going to pick up a Oracle book // on it but, I'm afraid that PL/pgSQL and PL/SQL aren't the same. // // Thanks // // Andy // // On Sat, 22 May 1999, dustin sallings wrote: // // > On Sat, 22 May 1999, Andy Lewis wrote: // > // > How can we tell you more if we don't know what you know? It's // > usually pretty safe to just go ahead and ask the question. You'll be // > redirected if you've posted to the wrong place. // > // > // I'd just plain would like to know more about PL/pgSQL. // > // // > // Andy // > // // > // On Sat, 22 May 1999, Piotr Stelmaszyk wrote: // > // // > // > I'd like to get to know where should I post messages concerning // > // > PL/pgSQL. // > // > // > // > // > // > /--------------------------------------------------------/ // > // > /- Piotr Stelmaszyk |---- Student of Computer Science ---/ // > // > /------------------ | at Poznan University of Technology / // > // > /----- mailto:kelman@fanthom.math.put.poznan.pl ---------/ // > // > /----- mailto:kelman@alpha.net.pl -----------------------/ // > // > /--------------------------------------------------------/ // > // > // > // > // > // > // > // // > // // > // // > // > -- // > Principal Member Technical Staff, beyond.com The world is watching America, // > pub 1024/3CAE01D5 1994/11/03 Dustin Sallings <dustin@spy.net> // > | Key fingerprint // > L______________________________________________ and America is watching TV. __ // > // // // - -- Principal Member Technical Staff, beyond.com The world is watching America, pub 1024/3CAE01D5 1994/11/03 Dustin Sallings <dustin@spy.net> | Key fingerprint L______________________________________________ and America is watching TV. __ ------------------------------ Date: Sat, 22 May 1999 21:49:21 -0700 From: ghoffman@ucsd.edu (Gary Hoffman) Subject: To: pgsql-general@postgreSQL.org subscribe end ------------------------------ Date: Sat, 22 May 1999 22:48:02 -0700 From: ghoffman@ucsd.edu (Gary Hoffman) Subject: Compile problem on BSDi 3.0 I suppose this is an oldie but goodie, but I need a clue. I've got BSDi 3.0 on an i386 platform. Following the installation instructions for pgsql, I upgraded flex to 2.5.4 using the 2.5.4a download from prep.ai.mit.edu. However, when I run gmake, I get this failure sequence: - ----------- gmake lexverify gmake[1]: Entering directory `/usr2/src/pgsql/src' gmake -C lextest all gmake[2]: Entering directory `/usr2/src/pgsql/src/lextest' lex scan.l gcc2 -c lex.yy.c gcc2 -c lextest.c gcc2 -o lextest lex.yy.o lextest.o unexpected last match in input() gmake[2]: Leaving directory `/usr2/src/pgsql/src/lextest' You have a buggy version of flex. Read INSTALL and search for flex for a fix. gmake[1]: *** [lexverify] Error 1 gmake[1]: Leaving directory `/usr2/src/pgsql/src' gmake: *** [all] Error 2 - -------------- My gcc is version 2.7.2.1, flex reports version 2.5.4. Can I buy a clue from someone? Thanks, Gary *************************************************************************** * Gary B. Hoffman, Computing Services Manager e-mail: ghoffman@ucsd.edu * * Graduate School of International Relations and Pacific Studies (IR/PS) * * University of California, San Diego (UCSD) voice: (619) 534-1989 * * 9500 Gilman Dr., La Jolla, CA 92093-0519 USA fax: (619) 534-3939 * ************************************************************************** ------------------------------ Date: Sun, 23 May 1999 17:04:50 +1200 From: Glen and Rosanne Eustace <agree@godzone.net.nz> Subject: Keyed Tables I thought I had already posted this query but now I can't remember. If I have please excuse the repeat. But as I can't remember the answer either can someone please comment. Is there likely to be any attempt to allow a table to be keyed. It seems that by default a table is created as a heap and in order to improve access speed, one must create indices on that table. I use Ingres at work and quite like the ability to do a 'modify table to btree' type of command. When the table concerned is basically only a key plus value, it seems rather inefficient to have to have both the heap and then an index when supposedly one could simply make the table into a btree in the first place. - -- Glen Eustace, on behalf of GodZone Internet Services, a division of AGRE Enterprises Limited. 176 Te Awe Awe St, Palmerston North, New Zealand Ph: +64 6 356 2562, Fax: +64 6 357 0271, Mobile: 025 416 184, http://WWW.GodZone.Net.NZ ------------------------------ Date: Sun, 23 May 1999 02:32:45 -0400 (EDT) From: Bruce Momjian <maillist@candle.pha.pa.us> Subject: Re: [GENERAL] Keyed Tables [Charset iso-8859-1 unsupported, filtering to ASCII...] > I thought I had already posted this query but now I can't remember. If > I have please excuse the repeat. But as I can't remember the answer > either can someone please comment. > > Is there likely to be any attempt to allow a table to be keyed. It > seems that by default a table is created as a heap and in order to > improve access speed, one must create indices on that table. > > I use Ingres at work and quite like the ability to do a 'modify table to > btree' type of command. When the table concerned is basically only a > key plus value, it seems rather inefficient to have to have both the > heap and then an index when supposedly one could simply make the table > into a btree in the first place. Yes, it is a nice feature, but we don't support it. We do have CLUSTER, but that is not as nice. - -- Bruce Momjian | http://www.op.net/~candle maillist@candle.pha.pa.us | (610) 853-3000 + If your life is a hard drive, | 830 Blythe Avenue + Christ can be your backup. | Drexel Hill, Pennsylvania 19026 ------------------------------ Date: Sun, 23 May 1999 02:33:17 -0400 (EDT) From: Bruce Momjian <maillist@candle.pha.pa.us> Subject: Re: [GENERAL] Compile problem on BSDi 3.0 Check your path, and delete configure.in so it sees flex, not lex. [Charset ISO-8859-1 unsupported, filtering to ASCII...] > I suppose this is an oldie but goodie, but I need a clue. > > I've got BSDi 3.0 on an i386 platform. Following the installation > instructions for pgsql, I upgraded flex to 2.5.4 using the 2.5.4a download > from prep.ai.mit.edu. However, when I run gmake, I get this failure > sequence: > > ----------- > > gmake lexverify > gmake[1]: Entering directory `/usr2/src/pgsql/src' > gmake -C lextest all > gmake[2]: Entering directory `/usr2/src/pgsql/src/lextest' > lex scan.l > gcc2 -c lex.yy.c > gcc2 -c lextest.c > gcc2 -o lextest lex.yy.o lextest.o > unexpected last match in input() > gmake[2]: Leaving directory `/usr2/src/pgsql/src/lextest' > > You have a buggy version of flex. Read INSTALL and search for flex for a > fix. > > gmake[1]: *** [lexverify] Error 1 > gmake[1]: Leaving directory `/usr2/src/pgsql/src' > gmake: *** [all] Error 2 > > -------------- > > My gcc is version 2.7.2.1, flex reports version 2.5.4. > > Can I buy a clue from someone? > > Thanks, > Gary > > *************************************************************************** > * Gary B. Hoffman, Computing Services Manager e-mail: ghoffman@ucsd.edu * > * Graduate School of International Relations and Pacific Studies (IR/PS) * > * University of California, San Diego (UCSD) voice: (619) 534-1989 * > * 9500 Gilman Dr., La Jolla, CA 92093-0519 USA fax: (619) 534-3939 * > ************************************************************************** > > > - -- Bruce Momjian | http://www.op.net/~candle maillist@candle.pha.pa.us | (610) 853-3000 + If your life is a hard drive, | 830 Blythe Avenue + Christ can be your backup. | Drexel Hill, Pennsylvania 19026 ------------------------------ Date: Sun, 23 May 1999 13:16:26 +0300 From: Herouth Maoz <herouth@oumail.openu.ac.il> Subject: Re: [GENERAL] postgres getting slow At 21:51 +0300 on 20/05/1999, Brian wrote: > What sort of things to do you catch with logging this? I haven't seen a > single thing goto this file since starting it: > > export PGLOGFILE> su postgres -c '/usr/bin/postmaster -B 250 -i -S -D/var/lib/pgsql -o -S >1024 >> ${PGLOGFILE} 2>&1' I usually add "-d 2" to my postmaster invocation. It puts a lot of information in the logfile, although I must say I've never been happy about Postgres's logs. If you want to see where an error has occured, the actual query is buried within many internal messages. Herouth - -- Herouth Maoz, Internet developer. Open University of Israel - Telem project http://telem.openu.ac.il/~herutma ------------------------------ Date: Sun, 23 May 1999 12:57:05 +0300 From: Herouth Maoz <herouth@oumail.openu.ac.il> Subject: Re: [GENERAL] Looking for Mr. Autonum At 23:07 +0300 on 19/05/1999, E Westfield wrote: > Greetings > Looking for how to build a table with a built in unique sequential numeric > key (primary optional) and then copy from a flat file to that same field. > Can not see on the _CREATE TABLE_ nor the _TYPE_ how to do so. Is the OID > mentioned in the _COPY_ a possible. > > I wish to have a new unique ID for any additions to the table without > haveing to programmatically create one. This is done in other databases so > I am sure it is available in Postgresql. Thank you for you help in this > slow learning one. This question is in the FAQ, ITEM 3.13: http://www.postgresql.org/docs/faq-english.shtml#3.13 Note that if you want to fill the table from a flat file that doesn't have the serial numbers, you have to take some steps. Suppose the name of the serial field is "s1", and the other fields are "f1", "f2"... "fn". 1) Create your table, say, "table1", with the fields s1, f1, f2... fn. 2) Create a temporary table "temp1", with only fields f1, f2... fn. 3) Use COPY to copy from the flat file to "temp1". 4) Use the following insert command to fill "table1": INSERT INTO table1 (f1, f2, ... fn) SELECT f1, f2,... fn FROM temp1; As you see, there is no mention of the s1 field, and since it has a default, it fills itself automatically. 5) Drop the temp1 table. Herouth - -- Herouth Maoz, Internet developer. Open University of Israel - Telem project http://telem.openu.ac.il/~herutma ------------------------------ Date: Sun, 23 May 1999 13:01:34 +0300 From: Herouth Maoz <herouth@oumail.openu.ac.il> Subject: RE: [GENERAL] For data based web site, which RDBMS is better & wh y ? At 00:59 +0300 on 20/05/1999, Jackson, DeJuan wrote: > The problem here is to find impartial comparisons. > The question between MySQL and PostgreSQL usually come down to > Do I care most about speed? - usually true for purely Web Apps. > or > Do I need transaction and the other features PostgreSQL offers? - > which tends to only be true if you plan on using the database for things > other than web development. To be more exact, you have to ask yourself whether only one person will be performing updates at a time. The lack of transactions for MySQL implies lack of locks, and thus lack of support for concurrent updates. Herouth - -- Herouth Maoz, Internet developer. Open University of Israel - Telem project http://telem.openu.ac.il/~herutma ------------------------------ Date: Mon, 24 May 1999 07:30:27 +1200 From: Glen and Rosanne Eustace <agree@godzone.net.nz> Subject: RE: [GENERAL] Keyed Tables > Yes, it is a nice feature, but we don't support it. We do > have CLUSTER, but that is not as nice. Any chance of adding it to the list of possible enhancements ? ------------------------------ Date: Sun, 23 May 1999 17:03:05 -0400 (EDT) From: Bruce Momjian <maillist@candle.pha.pa.us> Subject: Re: [GENERAL] Keyed Tables [Charset iso-8859-1 unsupported, filtering to ASCII...] > > Yes, it is a nice feature, but we don't support it. We do > > have CLUSTER, but that is not as nice. > > Any chance of adding it to the list of possible enhancements ? Not sure it is do-able for us. It would require so much work, that I hesitate to add it. - -- Bruce Momjian | http://www.op.net/~candle maillist@candle.pha.pa.us | (610) 853-3000 + If your life is a hard drive, | 830 Blythe Avenue + Christ can be your backup. | Drexel Hill, Pennsylvania 19026 ------------------------------ Date: Sun, 23 May 1999 19:21:08 -0500 (CDT) From: Andy Lewis <alewis@themecca.net> Subject: Full Text Searches Whats the possibility of having full text searches added to text fields? That would be awesome..... Andy ------------------------------ Date: Sun, 23 May 1999 22:26:08 -0400 (EDT) From: "Brett W. McCoy" <bmccoy@lan2wan.com> Subject: Re: [GENERAL] Full Text Searches On Sun, 23 May 1999, Andy Lewis wrote: > Whats the possibility of having full text searches added to text fields? > > That would be awesome..... Unfortunately, full text indexing is a different issue than the kind of indexing performed on table columns, and if you want to do any kind of efficient full text searching, you have to index the individual words in the text or it'd be so slow as to be hardly useful (especially if you're talking about 600,000 records with 2K of text in each text field). Excalibur, for instance, creates its own internal indexing for full text records, but uses an underlying SQL database for regular fielded data, and when you design your database, you have to make the distinction about what kind of indexing you want, stop words (words you don't want indexed, like 'the' and 'of'), and the way certain fields can or will be searched. Brett W. McCoy http://www.lan2wan.com/~bmccoy/ - ----------------------------------------------------------------------- The six great gifts of an Irish girl are beauty, soft voice, sweet speech, wisdom, needlework, and chastity. -- Theodore Roosevelt, 1907 ------------------------------ End of pgsql-general-digest V1 #325 ***********************************
pgsql-general by date: