Undeliverable Message - Mailing list pgsql-general

To:            ISMTP@SFRA0046@Servers[<pgsql-general-digest@hub.org>]
Cc:
Subject:       pgsql-general-digest V1 #329

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       Monday, May 24 1999       Volume 01 : Number 329



Index:

Re: [GENERAL] Problems with INSERT INTO?
pg_dump core dumps
Re: [GENERAL] PL/pgSQL - mailng list
size limits on insert/copy/etc

----------------------------------------------------------------------

Date: Mon, 24 May 1999 10:34:51 -0700 (PDT)
From: Dustin Sallings <dustin@spy.net>
Subject: Re: [GENERAL] Problems with INSERT INTO?

On Mon, 24 May 1999, Simon Drabble wrote:

# char query[LOTS_OF_ROOM];
# sprintf(query, "INSERT INTO octects VALUES(%d)", a);
#
# PQexec(conn, query);

    snprintf would probably be a better choice.

# -or- download my libpq wrapper, which allows you to perform queries without
# using a temporary char array, in a manner similar to printf(). Available via
# anon ftp from
#
# brainkarma.dyndns.org/pub/dblib/

    I was about to suggest something like this be part of the core
library.  It makes a lot of sense, and that's what vsnprintf is for.  :)

- --
SA, beyond.com           My girlfriend asked me which one I like better.
pub  1024/3CAE01D5 1994/11/03 Dustin Sallings <dustin@spy.net>
|    Key fingerprint L_______________________ I hope the answer won't upset her. ____________

------------------------------

Date: Mon, 24 May 1999 13:45:24 -0500
From: Ari Halberstadt <ari@shore.net>
Subject: pg_dump core dumps

Using pg_dump with 6.5b1 on solaris sparc, crashes with a core dump.

This means I can't keep backups and I can't upgrade my data model without
being able to export the old data.

If one of the developers wants debug info let me know what you need (e.g.,
what commands to run in gdb--though I'll have to install this or get run
permissions from the sysadmin).

- -- Ari Halberstadt mailto:ari@shore.net <http://www.magiccookie.com/>
PGP public key available at <http://www.magiccookie.com/pgpkey.txt>

------------------------------

Date: Mon, 24 May 1999 11:08:58 -0700 (PDT)
From: Dustin Sallings <dustin@spy.net>
Subject: Re: [GENERAL] PL/pgSQL - mailng list

On Tue, 25 May 1999, Chris Bitmead wrote:

    What does this have to do with pl/pgsql?

# It's extremely straight-forward..
# $q # $q->execute("foo");
# while (($x, $y, $z) #  #stuff
# }
#
# $q # $q->execute($x,$y,$z);
#
# Mike Haberman wrote:
# >
# > I too need more info on PL/pgSQL than the docs supply.
# >
# > Is it possible for people to mail me any examples of PL/pgSQL.  I
# > just need to see examples of the syntax of the various control
# > sturctures, variable assignment, and the like.
# >
# > >From simple to very complex, send anything that might be helpful.
# >
# > thanks a ton
# >
# > mike haberman
# > mikeh@ncsa.uiuc.edu
# >
# > >
# > > 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. __
# > >
# > >
#
# --
# Chris Bitmead
# http://www.bigfoot.com/~chris.bitmead
# mailto:chris.bitmead@bigfoot.com
#
#

- --
SA, beyond.com           My girlfriend asked me which one I like better.
pub  1024/3CAE01D5 1994/11/03 Dustin Sallings <dustin@spy.net>
|    Key fingerprint L_______________________ I hope the answer won't upset her. ____________

------------------------------

Date: Mon, 24 May 1999 23:15:21 +0100
From: John Browning <jb@poplar.com>
Subject: size limits on insert/copy/etc

I'm trying to add large text items to a table (field declared as type
text). PQSendQuery can't take more than 8192 bytes.That's OK. But COPY
also complains that tuples of 29896 bytes are too big (trying to copy
from a file). So how do I get big text fields into a table? Do I have to
make them large objects? (And, if so, in what sense is the text field of
"unlimited size"?) Or am I just missing something simple?

Many thanks in advance for any advice...

bests

- --

John Browning  //  71 Richmond Ave  //  London N1 0LX
t 44 171 700 1230  //  f 44 171 700 5255

------------------------------

End of pgsql-general-digest V1 #329
***********************************