Re: [GENERAL] Changing from default configuration options in 7.1?
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" in stop() is no longer long enough (on a dual-cpu PIII/650 machine!). So "pidof postmaster" returns a non-null value and *that* results in a syntax error: Checking postgresql installation: [ OK ] ./postgresql: [: 18209: unary operator expected ISTM that every occurrence of if [ $pid ] should be if [ -n "$pid" ] (I think the test should become something like "if [ -n "$pid" ];..." instead of just "if [ $pid ]", which at least prevents the syntax error...) Of course, fixing the syntax error isn't the main problem, which is that the shutdown of the old postmaster(s) hasn't completed yet, resulting in a "false positive" from the pidof operation. I bumped the "sleep 2" up to "sleep 5" and the problem went away. Surely there's a better fix? In the stop() function, I use: su -l postgres -c "/usr/bin/pg_ctl -D $PGDATA -w stop" with no sleep at all I sent both these changes to lamar during rc4, but I got no reply. I don't know if he got them and determined that my patches were worthless, or if they did not reach him. In any case, those two changes work for me. YMMV. -- Karl ---(end of broadcast)--- TIP 2: you can get off all lists at once with the unregister command (send "unregister YourEmailAddressHere" to [EMAIL PROTECTED])
[GENERAL] Re: Latin2 and Unicode problems
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 matter if I try to use
ISO8859-2 or Unicode client encoding, the db doesn't get it right - such
functions as upper/lower etc. give unpredictable results (as the result
of select upper('some-polish-chars') return even some three-byte unicode
chars). I quite frequently get the following message:
utf_to_latin: could not convert UTF-8 (0xc3a3) ignored
(the Unicode char code varies...)
--
Grzegorz Mucha [EMAIL PROTECTED] ICQ #91619595, tel.(502)261417
Quidquid id est, timeo Danaos et dona ferentes.
Wergiliusz, "Eneida"
---(end of broadcast)---
TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
RE: [GENERAL] Best practice
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: [EMAIL PROTECTED] Subject: Re: [GENERAL] Best practice [EMAIL PROTECTED] writes: We use Ingres where I work and when setting up a server we always try to ensure that the log and data files are on different spindles. This would be good practice in PG simply for performance reasons. Ideally the WAL log should be on a disk that has nothing else to do, so that you never have to seek somewhere else than the current WAL segment. I'm not sure that we can yet guarantee very much about recovery from disk hardware failures. regards, tom lane ---(end of broadcast)--- TIP 5: Have you checked our extensive FAQ? http://www.postgresql.org/users-lounge/docs/faq.html ---(end of broadcast)--- TIP 2: you can get off all lists at once with the unregister command (send "unregister YourEmailAddressHere" to [EMAIL PROTECTED])
Re: [GENERAL] Re: Latin2 and Unicode problems
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 support only?
Then, why you see following erros:
However, when creating db with Unicode, no matter if I try to use
ISO8859-2 or Unicode client encoding, the db doesn't get it right - such
functions as upper/lower etc. give unpredictable results (as the result
of select upper('some-polish-chars') return even some three-byte unicode
chars). I quite frequently get the following message:
utf_to_latin: could not convert UTF-8 (0xc3a3) ignored
(the Unicode char code varies...)
This kind of error messages should appear only when the unicode
support enabled. So I assume both locale support AND unicode support
are enabled...
That's because locale support (--enable-locale) does not consider
about the Unicode support. (that's not the locale support's fault,
since it was developped before the Unicode support appears). When you
create the unicode database, everything is represented in the UTF-8
encoding. However, the locale support thinks that it is ISO 8859-2 (in
your case) and it try to do the case conversion using the ISO 8859-2
locale. As a result, you see invalid UTF-8 sequences.
Does it match your situation?
--
Tatsuo Ishii
---(end of broadcast)---
TIP 2: you can get off all lists at once with the unregister command
(send "unregister YourEmailAddressHere" to [EMAIL PROTECTED])
[GENERAL] static variables in functions
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 - ---(end of broadcast)--- TIP 4: Don't 'kill -9' the postmaster
Re: [GENERAL] Re: Latin2 and Unicode problems
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) does not consider about the Unicode support. (that's not the locale support's fault, since it was developped before the Unicode support appears). When you create the unicode database, everything is represented in the UTF-8 encoding. However, the locale support thinks that it is ISO 8859-2 (in your case) and it try to do the case conversion using the ISO 8859-2 locale. As a result, you see invalid UTF-8 sequences. Does it match your situation? Actually, that may be it. I stopped getting the messages after compiling without locale support, but with Unicode. But there is still the problem of not working sorting and conversions. Only option I can think of would be to somehow set the system locale to pl_PL.UTF-8 (I don't even know if there's such option). Please let me know if there is another way to do it. -- Grzegorz Mucha [EMAIL PROTECTED] ICQ #91619595, tel.(502)261417 Quidquid id est, timeo Danaos et dona ferentes. Wergiliusz, "Eneida" ---(end of broadcast)--- TIP 3: if posting/reading through Usenet, please send an appropriate subscribe-nomail command to [EMAIL PROTECTED] so that your message can get through to the mailing list cleanly
[GENERAL] Database Connect
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 Postgresql 7.03. Is there some modifications between 7.03 and 7.1, or is it a bad config of my server ? Any help will be appreciated Thank's a lot Michael ---(end of broadcast)--- TIP 4: Don't 'kill -9' the postmaster
Re: [GENERAL] very slow execution of stored procedures
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 check this out (very simple) : Nobody else seems to have answered this yet, so I'll have a stab. -- CREATE FUNCTION finaliza_chamv2(INT4, INT4, INT4, CHAR(23), CHAR(23), CHAR(1), INT4, INT4, INT4, CHAR(23), INT4, INT4, CHAR(25), INT4, INT4, INT4) RETURNS int4 AS [snipped simple update function] If I change all variables to the parameters value inside the stored procedure and then execute the frist script, then it is very fast, check out execution time : 1ms now its time to do the same thing using the stored procedure : execution time : about 5s Is it supose to execute with different speed? What can I do to fix it? I'm using postgres RPM 7.0.3-2 in RedHat 6.2. Well - there are some differences - if I understand correctly, the parser is smarter about things when constants are explicitly specified (like in the quick example). I'm assuming your table is large and what is happening is that the function is not using indexes. The most likely reason I can see is the timestamp() calls in the code. If you do: select proname,proiscachable from pg_proc where proname='timestamp'; You'll see that the conversion functions are marked not cachable, so that would probably discourage the use of the index on the timestamp fields. Use another variable to hold the converted timestamp value and see if that helps. If you still don't get an improvement try passing in the values as timestamps rather than text. If that still doesn't help try: SET ENABLE_SEQSCAN = OFF; before calling the function and see what that does. If you are still having problems, can you supply the output of EXPLAIN for the fast version. ps: There are some specific procedures I needed to execute before I got pl/pgsql working : CREATE FUNCTION plpgsql_call_handler () RETURNS opaque AS '/usr/lib/pgsql/plpgsql.so' LANGUAGE 'C'; CREATE PROCEDURAL LANGUAGE 'plpgsql' HANDLER plpgsql_call_handler LANCOMPILER 'PL/PgSql internal'; A simpler method is to do: createlang plpgsql mydatabase from the command-line. HTH - Richard Huxton ---(end of broadcast)--- TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
Re: [GENERAL] password authentication
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 would need to do to activate the password authentication? Does the pg_hba.conf file have anything to do with this? If it does, and I only want to create a password for this one user, would I specify it in the pg_hba.conf file? Use pg_hba.conf to turn on password checking. Checking is done if the connection method, database (and connection source for TCP/IP) match a line in pg_hba.conf that requires it. You cannot turn on checking per _user_. It's all users or none. -- Oliver Elphick[EMAIL PROTECTED] Isle of Wight http://www.lfix.co.uk/oliver PGP: 1024R/32B8FAA1: 97 EA 1D 47 72 3F 28 47 6B 7E 39 CC 56 E4 C1 47 GPG: 1024D/3E1D0C1C: CA12 09E0 E8D5 8870 5839 932A 614D 4C34 3E1D 0C1C "For this reason I also suffer these things, but I am not ashamed; for I know whom I have believed, and am persuaded that He is able to keep that which I have committed unto him until that day." II Timothy 1:12 ---(end of broadcast)--- TIP 5: Have you checked our extensive FAQ? http://www.postgresql.org/users-lounge/docs/faq.html
Re: [GENERAL] PL/Perl Question
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 help would be appreciated. As I understand it, PL/Perl doesn't currently have an interface to the server backend, so all you can really do with it is string and number manipulation. You'll have to use Tcl or PL/PGSQL for your functions. -Doug -- The rain man gave me two cures; he said jump right in, The first was Texas medicine--the second was just railroad gin, And like a fool I mixed them, and it strangled up my mind, Now people just get uglier, and I got no sense of time... --Dylan ---(end of broadcast)--- TIP 2: you can get off all lists at once with the unregister command (send "unregister YourEmailAddressHere" to [EMAIL PROTECTED])
[GENERAL] Re: problems with pg_dumplo (was Re: backup with blobs)
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) Do you have right permissions for DB and dirs with LO dumps? yes, I'm in real god-mode. However: the problem is not happening on a new created database, so maybe there is a problem on my system. Hmm.. may be, sounds curious if everythig is right on mew DB. It is curious and I dont want play around any more on my testmachine. Later in the weekend I will jump into the production-server and dump all the stuff and try to restore the data in a new installed 7.1-environment. I'll post my success/failure here then. thnx, peter -- mag. peter pilsl phone: +43 676 3574035 fax : +43 676 3546512 email: [EMAIL PROTECTED] sms : [EMAIL PROTECTED] pgp-key available ---(end of broadcast)--- TIP 5: Have you checked our extensive FAQ? http://www.postgresql.org/users-lounge/docs/faq.html
Re: [GENERAL] very slow execution of stored procedures
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.
--
bxs=# SET ENABLE_SEQSCAN = OFF;
SET VARIABLE
bxs=# SELECT finaliza_chamv2(1,65535,49644,'2001-04-17 11:50:55','2001-04-17
12:17:40', '0', 0, 0, 48, '', 0, 10, '2817107', 0, 261, 65535);
finaliza_chamv2
-
0
(1 row)
Execution time = about 4s.
--
This time I'm trying to remove timestamp conversions from where clause:
DROP FUNCTION finaliza_chamv2(INT4, INT4, INT4, CHAR(23), CHAR(23), CHAR(1),
INT4, INT4, INT4, CHAR(23), INT4, INT4,
CHAR(25),
INT4, INT4, INT4);
CREATE FUNCTION finaliza_chamv2(INT4, INT4, INT4, CHAR(23), CHAR(23),
CHAR(1),
INT4, INT4, INT4, CHAR(23), INT4, INT4,
CHAR(25),
INT4, INT4, INT4) RETURNS int4 AS
'
DECLARE
pbxs ALIAS FOR $1;
pchave ALIAS FOR $2;
pidentificacao ALIAS FOR $3;
pdtinicial ALIAS FOR $4;
pdtfinal ALIAS FOR $5;
pflgliber ALIAS FOR $6;
ptempototalALIAS FOR $7;
pcodliber ALIAS FOR $8;
pddd ALIAS FOR $9;
pdtocupALIAS FOR $10;
pindicadoraALIAS FOR $11;
pcategoria ALIAS FOR $12;
pidentidadea ALIAS FOR $13;
pfds ALIAS FOR $14;
presultchamALIAS FOR $15;
pcifraorigem ALIAS FOR $16;
BEGIN
UPDATE cham_chamada
SET dt_final= TIMESTAMP(pdtfinal);
flg_liberacao = pflgliber,
temp_total = ptempototal,
cod_liberjuntor = pcodliber,
ddd = pddd,
indicadora = pindicadora,
cod_categoria = pcategoria,
identidadea = pidentidadea,
cod_fds = pfds,
cod_resultcham = presultcham,
cifra_origem= pcifraorigem
WHERE cod_bxs = pbxs AND
chave = pchave AND
identificacao = pidentificacao AND
dt_inicial= pdtinicial;
IF pdtocup THEN
UPDATE cham_servico
SET
dt_ocupacao = TIMESTAMP(pdtocup)
WHERE
cod_bxs = pbxs AND
chave = pchave AND
identificacao = pidentificacao AND
dt_inicial= tempo AND
dt_finalizacao is null;
END IF;
RETURN 0;
END;
'
LANGUAGE 'plpgsql';
bxs=# SELECT finaliza_chamv2(1,65535,49644,'2001-04-17 11:50:55','2001-04-17
12:17:40', '0', 0, 0, 48, '', 0,
10, '2817107', 0, 261, 65535);
Cancel request sent
ERROR: Query was cancelled.
Execution time : ?? (I was forced to abort after more than 1 minute waiting
and a lot of cpu was sucked while executing)
Note that execution time go back to 4seconds if I put the original stored
procedure back.
--
Here some info about my table and fast execution :
bxs=# EXPLAIN UPDATE cham_chamada
bxs-# SET dt_final = TIMESTAMP('2001-04-17 12:12:10'),
bxs-# flg_liberacao = '0',
bxs-# temp_total = 0,
bxs-# cod_liberjuntor = 0,
bxs-# ddd = 48,
bxs-# indicadora = 0,
bxs-# cod_categoria = 10,
bxs-# identidadea = '2817005',
bxs-# cod_fds = 0,
bxs-# cod_resultcham = 6,
bxs-# cifra_origem = 65535
bxs-# WHERE cod_bxs = 1 AND
bxs-# chave = 65535 AND
bxs-# identificacao = 49644 AND
bxs-# dt_inicial = TIMESTAMP('2001-04-17 12:12:00');
NOTICE: QUERY PLAN:
Index Scan using xpkcham_chamada on cham_chamada (cost=0.00..4.23 rows=1
width=58)
EXPLAIN
bxs=# \d cham_chamada
Table "cham_chamada"
Attribute|Type | Modifier
-+-+--
cod_bxs | integer | not null
chave | integer | not null
identificacao | integer | not null
dt_inicial | timestamp | not null
indicadora | integer |
cod_categoria | integer |
identidadea | varchar(20) |
dt_final| timestamp |
juntor | integer |
indicadorb | integer |
identidadeb | varchar(20) |
flg_chamada | char(1) |
flg_liberacao | char(1) |
temp_total | integer |
ddd | smallint|
cod_liberjuntor | integer |
cod_resultcham | integer |
cod_fds | integer |
cifra_origem| integer |
Indices: xie1cham_chamada,
xie2cham_chamada,
xpkcham_chamada
bxs=# SELECT COUNT(*) FROM cham_chamada;
count
145978
(1 row)
--
I found a solution that uses
[GENERAL] Logical expn not shortcircuiting in trigger function?
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 evaluating all the possibilities. For example: CREATE FUNCTION crash() RETURNS boolean AS ' BEGIN RAISE EXCEPTION ''crash()''; RETURN TRUE; -- will never get here END; ' LANGUAGE 'plpgsql'; SELECT 1 WHERE crash(); ERROR: crash() SELECT 1 WHERE 1=2 AND crash(); ?column? -- (0 rows) doesn't crash() because it realizes that, as both 1=2 and crash() must return true, that it isn't worth checking crash(). However, I have a procedure called by a trigger that is called for both INSERTs and UPDATEs. For INSERTs, we always want to check a class capacity. For UPDATEs, we only want to check the capacity if the registration status has changed: CREATE FUNCTION reg_chk_capacity() RETURNS opaque AS ' DECLARE seats int; BEGIN IF TG_OP=''INSERT'' OR (TG_OP=''UPDATE'' AND (OLD.statuscode NEW.statuscode)) THEN seats := Reg_SeatsLeft(NEW.InstID); IF seats 1 THEN RAISE EXCEPTION ''reg_chk_capacity__inst_filled: InstID=%, RegID=%'', NEW.InstID, NEW.RegID; END IF; END IF; RETURN NEW; END; ' LANGUAGE 'plpgsql'; (Reg_SeatsLeft() is a simple SQL function w/o any references to NEW or OLD) If I try to INSERT into this table, I get ERROR: record old is unassigned yet So, why hasn't the logic short-circuited? Am I missing something? -- Joel Burton [EMAIL PROTECTED] Director of Information Systems, Support Center of Washington ---(end of broadcast)--- TIP 4: Don't 'kill -9' the postmaster
Re: [GENERAL] Database Connect
=?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 undocumented and mostly-broken code in libpq that tried to be fancy about interpreting database names to mean more than just a database name. I don't recall all the arguments for taking it out versus trying to fix and document it, but the upshot was we took it out. regards, tom lane ---(end of broadcast)--- TIP 5: Have you checked our extensive FAQ? http://www.postgresql.org/users-lounge/docs/faq.html
[GENERAL] Re: problems with pg_dumplo (was Re: backup with blobs)
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 importing the blobs again, I always get the following error: lupo:/tmp/pgdump_lo # pg_dumplo -i -d peter -s ./ -u user -p pass 66611 blobtestlo_oid peter/blobtest/lo_oid/66611 66707 blobtestlo_oid peter/blobtest/lo_oid/66707 66867 blobtestlo_oid peter/blobtest/lo_oid/66867 skip approx.10 lines 70579 blobtestlo_oid peter/blobtest/lo_oid/70579 70643 blobtestlo_oid peter/blobtest/lo_oid/70643 pg_dumplo: lo_import: can't create inv object for ".//peter/blobtest/lo_oid/70643" pg_dumplo: ROLLBACK What do you do before this import? pg_dumplo -i (without -r) add *new* LO to DB and update LO oid in some tab.attr only. The option '-r' remove old LO and import new. Try: pg_dumplo -a -d my_db -s /my_dump/dir pg_dump [with relevant options for your DB] my.dump DROP DATABASE my_db; CREATE DATABASE my_db; psql my_db my.dump pg_dumplo -i -d my_db -s /my_dump/dir Karel -- Karel Zak [EMAIL PROTECTED] http://home.zf.jcu.cz/~zakkr/ C, PostgreSQL, PHP, WWW, http://docs.linux.cz, http://mape.jcu.cz ---(end of broadcast)--- TIP 3: if posting/reading through Usenet, please send an appropriate subscribe-nomail command to [EMAIL PROTECTED] so that your message can get through to the mailing list cleanly
[GENERAL] Re: static variables in functions
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. Can it be made thread-safe? The PG backend isn't multi-thread program. You can use "static", if you sure what you do :-) If you allocate it you must be sure if you use some persisten memory context or you can use native malloc(), ..etc. Or is possible define arbitrary function as cacheable. Karel -- Karel Zak [EMAIL PROTECTED] http://home.zf.jcu.cz/~zakkr/ C, PostgreSQL, PHP, WWW, http://docs.linux.cz, http://mape.jcu.cz ---(end of broadcast)--- TIP 3: if posting/reading through Usenet, please send an appropriate subscribe-nomail command to [EMAIL PROTECTED] so that your message can get through to the mailing list cleanly
[GENERAL] Re: problems with pg_dumplo (was Re: backup with blobs)
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 in some tab.attr only. The option '-r' remove old LO and import new. Try: pg_dumplo -a -d my_db -s /my_dump/dir pg_dump [with relevant options for your DB] my.dump DROP DATABASE my_db; CREATE DATABASE my_db; psql my_db my.dump pg_dumplo -i -d my_db -s /my_dump/dir 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) However: the problem is not happening on a new created database, so maybe there is a problem on my system. I will install 7.1 on a different machine and try if I can import all my data before migrating to 7.1 on a production-server. When I want to migrate _all_ data from one 7.1 to another 7.1 : does a brute filecopy do it ? Thanx a lot for your help, peter -- mag. peter pilsl phone: +43 676 3574035 fax : +43 676 3546512 email: [EMAIL PROTECTED] sms : [EMAIL PROTECTED] pgp-key available ---(end of broadcast)--- TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
[GENERAL] Re: PL/Perl Question
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. -- Travis Bauer | CS Grad Student | IU |www.cs.indiana.edu/~trbauer Hitesh Patel ([EMAIL PROTECTED]) wrote: 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 help would be appreciated. -- Hitesh Patel [EMAIL PROTECTED] ---(end of broadcast)--- TIP 5: Have you checked our extensive FAQ? http://www.postgresql.org/users-lounge/docs/faq.html ---(end of broadcast)--- TIP 6: Have you searched our list archives? http://www.postgresql.org/search.mpl
[GENERAL] I want to unsubscribe, how can i do it?
Tha is it! What I want to know is in this messages's subject. Thanks -- Guilherme Fortunato e-mail: [EMAIL PROTECTED] -- ---(end of broadcast)--- TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
[GENERAL] I want to unsubscribe!
-- Guilherme Fortunato e-mail: [EMAIL PROTECTED] -- ---(end of broadcast)--- TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
Re: [GENERAL] Database Connect
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 any idea what we should do now?
Thanks for all the effort that you guys have put into Postgres--if I was
following pgsql-hackers I probably could have put my 2 cents in earlier.
W
Tom Lane wrote:
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.
---(end of broadcast)---
TIP 2: you can get off all lists at once with the unregister command
(send "unregister YourEmailAddressHere" to [EMAIL PROTECTED])
