Dr. Evil <[EMAIL PROTECTED]> wrote:
> pl/pgsql doesn't seem to be very well documented. It would be cool if it
> were better documented, or if there were a tutorial.
Have you had a look at the materials at
http://www.brasileiro.net/postgres/'
?
Ray
--
I keep pitching my epic space oper
Nils Zonneveld <[EMAIL PROTECTED]> wrote:
> I'm searching for a web hosting company that also supports PostgreSQL
> and that is based in the Netherlands. Does anyone know a good one?
Ones that I'm aware of are
- Business Internet Trends, http://www.bit.nl
- Cistron Internet Services, http://www.c
Bruce Momjian <[EMAIL PROTECTED]> wrote:
>Especially Linux's ext2 vs. BSD's UFS.
Hmm.. Could you elaborate on that?
Commonly perceived problems with ext2:
- Lack of journalling
This can be fixed by upgrading to ext3, or switching to ReiserFS,
XFS or JFS (ReiserFS works well in
will trillich <[EMAIL PROTECTED]> wrote:
>On Thu, Apr 26, 2001 at 05:20:53PM +0200, Peter Eisentraut wrote:
>> See contrib/pgcrypto for hashing functions.
>Care to explain -- in terms a Debian newbie might grok -- what
>"contrib/pgcrypto" means?
Peter is referring to a directory in the PostgreSQ
Bob Parkinson <[EMAIL PROTECTED]> wrote:
>query: rollback
>
>does this mean that a transaction has failed?
Indeed.
>I'm not seeing any other error messages
A rollback need not be the result of the backend raising an error. It can
also be triggered deliberately by your code that talks to the bac
Peter Keller <[EMAIL PROTECTED]> wrote:
>we are running PostgreSQL 7.0.2 on Solaris 2.6,/x86 compiled by gcc 2.8.1.
There are at least two components in this you might consider upgrading:
- PostgreSQL itself (to 7.0.3 or, even better, 7.1)
- gcc. Gcc 2.8.1 was a bit of a dead end in gcc developme
Matthew Hixson <[EMAIL PROTECTED]> wrote:
>Which is the most recent version of Postgres, 7.1 or 7.1rc4 ?
7.1. (7.1 is the released version, 7.1rc4 was release candidate 4 for that
version)
HTH,
Ray
--
Do Microsoft's TCO calculations include TC of downtime?
---(end of b
Stan Brown <[EMAIL PROTECTED]> wrote:
>I am having a bit of trouble geting PostgreSQL working quite corectly on my
>fresh Debian "stable" istall.
>
>I installed it using the Debina dselect tool. Now, If I su - postgres, I
>can use psql to connect to the db, so I know that that part of the install
DaVinci <[EMAIL PROTECTED]> wrote:
> ERROR: Unrecognized language specified in a CREATE FUNCTION: 'plpgsql'.
> I use Debian packages for Pg 7.1 BETA4. I thought plpgsql was integrated by
> default, but see it is not so.
I have the same problem with 7.1RC2 built using Oliver's Debian diff f
DaVinci <[EMAIL PROTECTED]> wrote:
> When I am in middle of transaction and there is an error, for example
> caused by trying to insert a tupla with a "not null" value without valor,
> I get error:
>
> NOTICE: current transaction is aborted, queries ignored until end of
> transaction b
[EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
>I'm running postgresql-7.0.2-6 on a Debian potato.
Any particular reason why you're not running 7.0.3 (which is the latest
release and contains fixes for some problems with 7.0.2)?
Ray
--
"People should never have been given free will." Lots of lan
Jonas Lindholm <[EMAIL PROTECTED]> wrote:
>I'm running PG 7.0.3 on Linux where the maximum file size is 2GB
That's somewhat misleading. It's more accurate to state that GNU/Linux on
32bit architectures, for some combinations of kernel and C library, has a
maximum file size of 2GB.
Your options t
Daniel A. Melo <[EMAIL PROTECTED]> wrote:
>/usr/lib/gcc-lib/i386-conectiva-linux/2.95.3/include/limits.h:117:
>limits.h: Arquivo ou diretório não encontrado
I'll assume that's "no such file or directory".
>The line 117 from limits.h has:
>
>#ifndef _GCC_NEXT_LIMITS.H
>#include_next ...
>
>What s
Christopher Sawtell <[EMAIL PROTECTED]> wrote:
>a) Does VACUUMing ( with ANALYSE ) in effect perform a file consistency
>check on the database structure as a side effect?
As I understand it, it is more of a cleanup than a file consistency check.
>b) Is it ok to VACUUM while the database is aliv
On Fri, Jan 19, 2001 at 21:29:41 +1100, Matthew Taylor wrote:
> Umm I must have missed it in the manual, (read it 3-4 times tho) but what
> is the equivalent data dictionary structure in Postgres to the following
> in Oracle.
>
> Select table_name from user_tables;
> etc various special tabl
On Thu, Jan 18, 2001 at 22:30:48 +1300, Dan Langille wrote:
> When will 7.1 leave beta (roughly)?
>From what I've been reading on the lists, "soon". I suspect within the next
month or two.
> How stable is it? FWIW, I'll be using it for development, not production
I've not tested it extensivel
On Thu, Jan 11, 2001 at 20:06:33 +0100, Christian Pomar wrote:
> Using phorum (www.phorum.org) based on PHP, I am getting the following
> error when trying to insert a message in the PosgreSQL 6.5.3 database:
>
> ProcessQuery
> ERROR: Tuple is too big: size 12440
There is an 8K tuple length in
On Sun, Jan 14, 2001 at 23:27:06 +1300, Dan Langille wrote:
> I'm writing some stuff in PL/pgsql (actually, a lot of stuff). I have a
> question: At various times, it does UPDATEs. Is there a way to tell if
> the UPDATE actually affected any rows or not? I couldn't see how to get
> UPDATE to re
[Please don't mail in HTML]
On Thu, Jan 11, 2001 at 21:02:56 -, Guang Mei wrote:
>It seems to me that postgresql db's default set for commit is "on".
Erm, it's not PostgreSQL itself, but rather the "psql" interface.
> I would like to set it to "off". How could I do that?
By explicitly
19 matches
Mail list logo
