Steve Wampler wrote:
I just upgraded from 7.0.3 to 7.1 (using the RH rpms) with no
major problems. Nice!
However, I'm getting some strange behaviour from the init
script (/etc/rc.d/init.d/postgresql). In particular, a
restart when the database is running fails because the
"sleep 2"
Well, I didn't state it correctly, then. When I use iso8859-2, Postgres is
compiled with --enable-locale only (though compiling it with UNICODE
support, then creating database with ISO encoding works fine - sorting,
upper/lower case conversion).
However, when creating db with Unicode, no
What would the the best choice for the WAL mirroring, raid3 or 5. How big
does the WAL grow? mirroring is fine as long as the size isn't too big.
--
Ian Willis
-Original Message-
From: Tom Lane [mailto:[EMAIL PROTECTED]]
Sent: Friday, 20 April 2001 9:22 AM
To: [EMAIL PROTECTED]
Cc:
Well, I didn't state it correctly, then. When I use iso8859-2, Postgres is
compiled with --enable-locale only (though compiling it with UNICODE
support, then creating database with ISO encoding works fine - sorting,
upper/lower case conversion).
I'm confused. Did you enable the locale
hello everyone,
is there any possibility to keep the value of an arbitrary type variable in a plpgsql
function between its invocations?
If not, can it be made with functions written in C instead? I've "static storage" in
my mind.
Can it be made thread-safe?
- Papp Gyozo -
I'm confused. Did you enable the locale support only?
Sorry then. Well, I tested two cases:
- pg compiled only with enable locale and iso8859-2 works
- pg compiled with locale, enable unicode and unicode conversion doesn't
work as it should.
That's because locale support (--enable-locale)
Hi,
I installed Postgresql 7.1 (RPMs for Redhat 7.0).
When I start psql with the command 'psql mydb', everything's ok
But whan I start psql with the command 'psql mybase@myhost' I receive :
psql: FATAL 1: Database "mybase@myhost" does not exist in system catalog
I used this syntax with
From: "Vilson farias" [EMAIL PROTECTED]
Greetings,
I found something very weird related with stored procedures execution.
I
have this stored procedure to finalize a phone call, writing tha time of
call finalization and some other values to a calls table, called
cham_chamada. Please
Phuong Ma wrote:
Hi,
I was wondering what the different methods of creating a password
accomplish because I created a password for a test user using the
command WITH PASSWORD. I tried testing to see if I could log on without
a password, and it worked. Is there anything else I
Hitesh Patel [EMAIL PROTECTED] writes:
I need to be able to execute SQL commands from inside a plperl
function and can't figure if I can do this. Also.. after executing
the query I need to be able to grab the number of tuples returned
and there values.. how would I go about doing this.. any
On Fri, Apr 20, 2001 at 12:48:36PM +0200, Karel Zak wrote:
when working on an own database things works perfect. However I have a
reproduceable problem on a different database when importing blobs
into a single table while the old blobs still existing (no matter if
using -r or not)
Richard,
I've tried all your advices and still nothing.
It's been very hard to me understand why this is happening. The only
solution is to modify the stored procedure.
Problem: PostgreSQL apparently isn't short-circuiting a logical
expression, causing an error when it tries to evaluate OLD in an
INSERT trigger.
PostgreSQL normally 'short-circuits' logical expressions; that is,
once it figures out that it can't resolve an expression to truth,
it stops
=?iso-8859-1?Q?Micha=EBl_Fiey?= [EMAIL PROTECTED] writes:
But whan I start psql with the command 'psql mybase@myhost' I receive :
psql: FATAL 1: Database "mybase@myhost" does not exist in system catalog
This syntax isn't supported.
I used this syntax with Postgresql 7.03.
There was some
On Fri, Apr 20, 2001 at 02:12:23AM +0200, Peter Pilsl wrote:
On Wed, Apr 18, 2001 at 06:07:33PM -0400, Tom Lane wrote:
No need to re-invent the wheel; use the attached.
Thanx to Tom for this great tool.
Sure :-)
Unfortunately it does not work in my testenvironment.
When
On Fri, Apr 20, 2001 at 10:35:36AM +0200, Gyozo Papp wrote:
hello everyone,
is there any possibility to keep the value of an arbitrary type variable in a
plpgsql function between its invocations?
If not, can it be made with functions written in C instead? I've "static storage" in
my mind.
On Fri, Apr 20, 2001 at 10:27:11AM +0200, Karel Zak wrote:
Thanx to Tom for this great tool.
Sure :-)
sorry !! I ment to say, Thnx for giving this tool to me. Even more
thanx for writing this great tool to you !! :)
pg_dumplo -i (without -r) add *new* LO to DB and update LO oid
I think this is problematic with the default compilation fo PL/Perl.
The perl interpretor you get in a plperl function is inside of a
"sandbox" (can't remember the official name) where it is limited
to only a relatively small set of functions. I don't think that
SQL commands are included.
--
Tha is it! What I want to know is in this messages's subject.
Thanks
--
Guilherme Fortunato
e-mail: [EMAIL PROTECTED]
--
---(end of
--
Guilherme Fortunato
e-mail: [EMAIL PROTECTED]
--
---(end of broadcast)---
TIP 1: subscribe and unsubscribe commands go
Aahh! I have a million Perl scripts that rely on this syntax in the DBI
to connect to remote databases.
like:
$dbh=DBI-connect( "dbi:Pg:dbname=datab@remotehost",'wsprague','pass',
{RaiseError = 1, AutoCommit = 1})
or print STDERR "$DBI::errstrp";
Umm, do you have
21 matches
Mail list logo
