Re: [GENERAL] pg_dump, bytea, dump order questions
Hi Shridhar, thank you for your reply. It is really a good idea. I'll think it over. Many thanks, -- Csaba > -Original Message- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] Behalf Of Shridhar > Daithankar > Sent: 2004. június 7. 13:59 > To: [EMAIL PROTECTED] > Cc: '[EMAIL PROTECTED] (E-mail)' > Subject: Re: [GENERAL] pg_dump, bytea, dump order questions > > > Együd Csaba wrote: > > > Hi, > > answering partially my questions the first problem is > actualy solved. My > > text editor inserted a linebreak into the middle of the row > at position > > 16384. :) Should change my editor...??? :) > > > > The other question is yet a question. Is there any way to > dump first the > > functions and then the table definitions? > > If you have the functions in separate schema/database, you > can manually > dump/restore that first. > > HTH > > Shridhar > > ---(end of > broadcast)--- > TIP 2: you can get off all lists at once with the unregister command > (send "unregister YourEmailAddressHere" to > [EMAIL PROTECTED]) > > --- > Incoming mail is certified Virus Free. > Checked by AVG anti-virus system (http://www.grisoft.com). > Version: 6.0.699 / Virus Database: 456 - Release Date: 2004. 06. 04. > --- Outgoing mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.699 / Virus Database: 456 - Release Date: 2004. 06. 04. ---(end of broadcast)--- TIP 2: you can get off all lists at once with the unregister command (send "unregister YourEmailAddressHere" to [EMAIL PROTECTED])
[GENERAL] Index question
I have a query which orders data like this: ORDER BY a.col1, b.col2 where a and b are different tables. Both tables are really big and so, ordering takes quite a while. Now i would like to create an index to speed things up, but i don't know how to create such an index that would cover both columns in different tables. Regards, Kostko. -- Kostko <[EMAIL PROTECTED]> JWeb-Network ---(end of broadcast)--- TIP 2: you can get off all lists at once with the unregister command (send "unregister YourEmailAddressHere" to [EMAIL PROTECTED])
[GENERAL] contents of pg_database vanished..
Hi, I'm having some problems with pg_database -system table. It lost all of it's contents while database was running. It's actually still running but I don't know what to do because I'm not sure if it will start up at all after shutdown. I noticed the problem while trying to use pg_dump: [EMAIL PROTECTED]:~$ /usr/local/pgsql/bin/pg_dump -Ugalleria galleria pg_dump: missing pg_database entry for database "galleria" I could probably insert the missing row to pg_database but there are some columns I'm not sure about. What are datlastsysoid, datvacuumxid and datfrozenxid? Btw, pg version is 7.4.1 Thanks.. |\__/| ( oo )Kari Lavikka - [EMAIL PROTECTED] - (050) 380 3808 __ooO( )Ooo___ _ ___ _ _ _ __ _ _ "" ---(end of broadcast)--- TIP 8: explain analyze is your friend
Re: [GENERAL] [HACKERS] CREATE DATABASE on the heap with PostgreSQL?
Hi, The original poster seemed not to care too much about whether the data in this database is persistent. Under that assumption, I wonder if it's possible to do the following: 1- start postmaster 2 - create database on RAM disk (will be easy once tablespaces are there) 3 - work with this database 4 - postmaster shuts down / reboot server 5 - start postmaster 6 - create database ... The question is whether 5/6 will work, as the database will have entries in the system catalogs, and since the data of the database has disappeared. I.e. postmaster will probably complain mightly on startup. Perhaps it's possible to first start postmaster in single user mode to clean up the system catalogs? Maarten ---(end of broadcast)--- TIP 6: Have you searched our list archives? http://archives.postgresql.org
Re: [GENERAL] Backup and Restore of PostgreSQL
Easiest thing to do is to call pgsql from your servlet, have it dump the file somewhere in your web apps directory, and then either send the link to that file to the client or automatically forward the client there. Option 2 would be to use JDBC to view the meta data of the table and use it to write "CREATE" statements, and then build inserts from this data, but this would be very time consuming and difficult to do. Thanks! ~ Troy Campano ~ -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Richard Huxton Sent: Monday, June 07, 2004 9:57 AM To: Tim Penhey Cc: pgsql-general Subject: Re: [GENERAL] Backup and Restore of PostgreSQL Tim Penhey wrote: > Richard Huxton mentioned: > >> >>The pg_dump utility is the standard way to backup PostgreSQL and the >>custom format is already compressed. > The question though is how to call this from a java servlet / hopefully in a OS > independant way. Well, obviously file-paths can be dealt with simply, and pg_dump will output to a named file, so you're ok there. As for safely calling external programs, that's probably more a question for the servlet system (Tomcat I think you said) - it's not different to calling any other external program. -- Richard Huxton Archonet Ltd ---(end of broadcast)--- TIP 7: don't forget to increase your free space map settings ---(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
Re: [GENERAL] contents of pg_database vanished..
Kari Lavikka <[EMAIL PROTECTED]> writes: > I noticed the problem while trying to use pg_dump: >[EMAIL PROTECTED]:~$ /usr/local/pgsql/bin/pg_dump -Ugalleria galleria >pg_dump: missing pg_database entry for database "galleria" Hm. The row must still be there, else you could not have got that far. If you do "select * from pg_database", do you see all the rows you expect? How about "select * from pg_database where datname = 'galleria'"? If you see the row with an unqualified select but not with "where datname =", then I'd bet on the index for pg_database.datname being corrupted. You should be able to fix this with REINDEX. Since pg_database is a shared catalog, that will mean shutting down the postmaster --- read the details in the REINDEX man page. regards, tom lane ---(end of broadcast)--- TIP 6: Have you searched our list archives? http://archives.postgresql.org
Re: [GENERAL] [HACKERS] CREATE DATABASE on the heap with PostgreSQL?
Maarten Boekhold <[EMAIL PROTECTED]> writes: > The original poster seemed not to care too much about whether the data > in this database is persistent. Under that assumption, I wonder if it's > possible to do the following: > 1- start postmaster > 2 - create database on RAM disk (will be easy once tablespaces are there) > 3 - work with this database > 4 - postmaster shuts down / reboot server > 5 - start postmaster > 6 - create database ... > The question is whether 5/6 will work, as the database will have entries > in the system catalogs, and since the data of the database has > disappeared. I.e. postmaster will probably complain mightly on startup. You'd probably have to do a manual "DELETE FROM pg_database" to get rid of the row, but as of right now I don't think there'd be any other cleanup needed. The tablespace patch might complicate the picture though. regards, tom lane ---(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
Re: [GENERAL] How to find out who is calling the function
Why not use CURRENT_USER? -Original Message-From: BARTKO Zoltan [mailto:[EMAIL PROTECTED]Sent: Friday, June 04, 2004 10:34 PMTo: [EMAIL PROTECTED]Subject: [GENERAL] How to find out who is calling the function Dear friends, I had a look at www.pgsql.ru, looking for how to find out what user is calling the function - from inside the function. No luck. Could someone enlighten me: I have a stored function. I want to do the following: if caller() = ''userA'' then return -1; -- error else return 0; end if; -- OK caller() is the function I am looking for. Is there any function like this? If not, is there a way how to write one? Thanks Zoltan
[GENERAL] postgres on SuSE 9.1
Dear my friends... Usually I use MySQL. Now I have to migrate my database from MySQL to Postgres. I have created a database successfully with "creatdb" and a user account successfully. But I can not access the postgres with pgaccess. I found this error message : " Error trying to connect to database 'custadm' on host localhost PostgreSQL error message: Connection to database failed could not create socket: ©Hÿ¿pHÿ¿lHÿ¿ " Error in startup script: window ".pgaw:OpenDB" was deleted before its visibility changed while executing "tkwait visibility .pgaw:OpenDB" (procedure "::Connections::openConn" line 40) invoked from within "::Connections::openConn $i 1" (procedure "main" line 63) invoked from within "main $argc $argv" (file "/usr/bin/pgaccess" line 810) [EMAIL PROTECTED]:~> " Here what I have done " [EMAIL PROTECTED]:~> su Password: patrix:/localhome/patrixlinux # su postgres [EMAIL PROTECTED]:/localhome/patrixlinux> cd [EMAIL PROTECTED]:~> psql custadm Welcome to psql 7.4.2, the PostgreSQL interactive terminal. Type: \copyright for distribution terms \h for help with SQL commands \? for help on internal slash commands \g or terminate with semicolon to execute query \q to quit custadm=# create user someone with password 'pass_me' createdb; CREATE USER custadm=# " Anybody would be so nice to tell me why I can not access my postgres with pgaccess? Thank you very much in advance. __ Do you Yahoo!? Friends. Fun. Try the all-new Yahoo! Messenger. http://messenger.yahoo.com/ ---(end of broadcast)--- TIP 5: Have you checked our extensive FAQ? http://www.postgresql.org/docs/faqs/FAQ.html
Re: [GENERAL] Tsearch case sensitive with dotted search terms.
Use tsearch2, tsearch is marked as obsolet :) More serious: apply attached patch, recompile and reinstall contrib/tsearch module. Patch commited to 7.3,7.4 and 7.5 branches, it fix asymetrical lexeme processing for text and query. Rajesh Kumar Mallah wrote: Hi, I think when search terms have "."s in them they become case sensitive in tsearch searches. How can we make them insensitive? Regds Mallah. tradein_clients=# SELECT co_name , co_name_index from iid_listing where co_name_index ## 'a.u.m&logistics'; ++--+ | co_name | co_name_index | ++--+ | A.U.M. LOGISTICS (I) PVT. LTD. | 'ltd' 'pvt' 'a.u.m' 'logist' | | A.U.M. LOGISTICS (I) PVT. LTD. | 'ltd' 'pvt' 'a.u.m' 'logist' | | A.U.M. LOGISTICS (INDIA) PVT. LTD. | 'ltd' 'pvt' 'a.u.m' 'india' 'logist' | ++--+ (3 rows) Time: 404.543 ms tradein_clients=# SELECT co_name , co_name_index from iid_listing where co_name_index ## 'a.u.m&LOGISTICS'; ++--+ | co_name | co_name_index | ++--+ | A.U.M. LOGISTICS (I) PVT. LTD. | 'ltd' 'pvt' 'a.u.m' 'logist' | | A.U.M. LOGISTICS (I) PVT. LTD. | 'ltd' 'pvt' 'a.u.m' 'logist' | | A.U.M. LOGISTICS (INDIA) PVT. LTD. | 'ltd' 'pvt' 'a.u.m' 'india' 'logist' | ++--+ (3 rows) Time: 425.697 ms tradein_clients=# SELECT co_name , co_name_index from iid_listing where co_name_index ## 'A.U.M&LOGISTICS'; +-+---+ | co_name | co_name_index | +-+---+ +-+---+ (0 rows) -- Teodor Sigaev E-mail: [EMAIL PROTECTED] tp.gz Description: Unix tar archive ---(end of broadcast)--- TIP 6: Have you searched our list archives? http://archives.postgresql.org
Re: [GENERAL] Backup and Restore of PostgreSQL
Well you might want to make sure the servlet only does one pg_dump at a time to a particular file in a secured directory (making sure you don't have any funny symlink problems) and all that sort of boring security, reliability and predictability stuff. Don't forget the UI. The dump could take a while. At 11:27 AM 6/7/2004 -0400, Campano, Troy wrote: Easiest thing to do is to call pgsql from your servlet, have it dump the file somewhere in your web apps directory, and then either send the link to that file to the client or automatically forward the client there. Option 2 would be to use JDBC to view the meta data of the table and use it to write "CREATE" statements, and then build inserts from this data, but this would be very time consuming and difficult to do. ---(end of broadcast)--- TIP 8: explain analyze is your friend
Re: [GENERAL] Index question
At 04:39 PM 6/7/2004 +0200, Jernej Kos wrote: I have a query which orders data like this: ORDER BY a.col1, b.col2 where a and b are different tables. Both tables are really big and so, ordering takes quite a while. Now i would like to create an index to speed things up, but i don't know how to create such an index that would cover both columns in different tables. How about creating two indexes. One index for each column of the DB. Try it. It could still speed things up. ---(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] postgres on SuSE 9.1
Prabu Subroto <[EMAIL PROTECTED]> wrote: > Dear my friends... > > Usually I use MySQL. Now I have to migrate my database > from MySQL to Postgres. > > I have created a database successfully with "creatdb" > and a user account successfully. > > But I can not access the postgres with pgaccess. > > I found this error message : > " > Error trying to connect to database 'custadm' on host > localhost > > PostgreSQL error message: Connection to database > failed > could not create socket: __HpHlH > " > Error in startup script: window ".pgaw:OpenDB" was > deleted before its visibility changed > while executing > "tkwait visibility .pgaw:OpenDB" > (procedure "::Connections::openConn" line 40) > invoked from within > "::Connections::openConn $i 1" > (procedure "main" line 63) > invoked from within > "main $argc $argv" > (file "/usr/bin/pgaccess" line 810) > [EMAIL PROTECTED]:~> > " > > Here what I have done > " > [EMAIL PROTECTED]:~> su > Password: > patrix:/localhome/patrixlinux # su postgres > [EMAIL PROTECTED]:/localhome/patrixlinux> cd > [EMAIL PROTECTED]:~> psql custadm > Welcome to psql 7.4.2, the PostgreSQL interactive > terminal. > > Type: \copyright for distribution terms >\h for help with SQL commands >\? for help on internal slash commands >\g or terminate with semicolon to execute query >\q to quit > > custadm=# create user someone with password 'pass_me' > createdb; > CREATE USER > custadm=# > " > > Anybody would be so nice to tell me why I can not > access my postgres with pgaccess? > > Thank you very much in advance. I would guess that Posgres is not listening on an IPv4 socket. I think pgaccess always connects via an IPv4 socket. (may be wrong here ...) Anyway, check your postgresql.conf file to see if the option to listen on a tcp/ip port is turned on. If not, that's almost definately your problem. -- Bill Moran Potential Technologies http://www.potentialtech.com ---(end of broadcast)--- TIP 7: don't forget to increase your free space map settings
Re: [GENERAL] Timestamp precision and rounding
Stephan Szabo wrote: On Thu, 3 Jun 2004, Jeff Boes wrote: (asked last week on .questions, no response) Can anyone explain why this happens? (under 7.4.1) select '2004-05-27 09:00:00.51-04' :: timestamp(0) ; timestamp - 2004-05-27 09:00:01 select '2004-05-27 09:00:00.50-04' :: timestamp(0) ; timestamp - 2004-05-27 09:00:00 That is, why doesn't the second operation result in the same timestamp as the first? Is it a floating-point representation issue, or are the mathematical rules of rounding not being followed correctly (as I understand them, anyway)? My first guess would be that your system probably implements its default rounding as nearest even for .5 results, what does 9:00:01.5 give you? 2004-05-27 09:00:02, so I guess that would confirm it. -- Jeff Boes vox 269.226.9550 ext 24 Database Engineer fax 269.349.9076 Nexcerpt, Inc. http://www.nexcerpt.com ...Nexcerpt... Extend your Expertise ---(end of broadcast)--- TIP 6: Have you searched our list archives? http://archives.postgresql.org
[GENERAL] Identifying the 'current user' when using a connection pool
We have a database that sets a column called MOD_BY = CURRENT_USER to almost all tables on INSERT and UPDATE. But now that the application is n-tier, and uses connection pools, the current_user no longer reflects the 'application user'. Is there any way to temporarily alter 'current_user' with an alias for the duration of a transaction? IE .. Any other suggestions on how to transition end-user identity in a connection pool environment? Thanks, Jack Jack KerkhofResearch & Developmentjack.kerkhof@guest-tek.comwww.guest-tek.com1.866.509.1010 3480 Guest-Tek (TSX:GTK) is a global provider of technology solutions to the hospitality industry. Endorsed by more major hotel chains than any of its competitors, Guest-Tek has installed its solutions in more than 570 hotels worldwide.
Re: [GENERAL] CREATE DATABASE on the heap with PostgreSQL?
Gaetano Mendola <[EMAIL PROTECTED]> wrote in message news:<[EMAIL PROTECTED]>... > If you access a table more frequently then other and you have enough > RAM your OS will mantain that table on RAM, don't you think ? > BTW if you trust on your UPS I'm sure you are able to create a RAM > disk and place that table in RAM. > > > Regards > Gaetano Mendola RAMdisks still need a hard disk drive to operate. I am talking here about entirely diskless configurations. Well, maybe as I suspected there is no technical explanation why this design decision has been made. When I have more time I will run a bechmark to check to which extent it does make a difference. I mean running the application from RAM and letting the DBMS know about it instead of letting the OS figure it out. ---(end of broadcast)--- TIP 2: you can get off all lists at once with the unregister command (send "unregister YourEmailAddressHere" to [EMAIL PROTECTED])
[GENERAL] bug in 7.4.2, concern unicode and russian content of db
There is bug in 7.4.2, concerning unicode and russian letters. For db in unicode russian data doesn`t order in alphabetical order (rows group with the same first letter but not in alphabetical order). SELECT "person" from my_table ORDER BY "person"; Rows group in such order (approximately): Ð-Ð-Ð-Ð-Ð, but must be : Ð-Ð-Ð-Ð-Ð. For english letters all looks fine. For db in koi8r encoding also all works right. So, I CANNOT use unicode with russian content of db in postgres. Is it bug or not? ---(end of broadcast)--- TIP 9: the planner will ignore your desire to choose an index scan if your joining column's datatypes do not match
Re: [GENERAL] COPY error handling
Bruno Wolff III wrote: On Fri, Jun 04, 2004 at 14:11:19 +, Bricklen <[EMAIL PROTECTED]> wrote: Hi, I'm not sure if this is the correct group for this question, but I'll post it hoping that it is. I'm loading several ~15 million row files into a table using the COPY command. Apparently one of the rows, about 6 million in, has an invalid entry. This is causing the COPY command to fail, so my question is this: Is there any way to skip invalid rows? Or send them to a separate log file etc to go through later? I've gone through the docs, but I didn't see anything specific to this. Any information, links, or hints are greatly appreciated. Currently there isn't a builtin way to do this. You can pass the data through a filter script that removes rows that are not in a proper format. Thanks for the clarification! Cheers, Bricklen ---(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
Re: [GENERAL] Dropping schemas and "illegal seek" -- MEA CUPLA
>>In article <[EMAIL PROTECTED]>, Felix Finch <[EMAIL PROTECTED]> writes: > I have a perl test program ... and began getting this complaint > from psql: > Can't drop schemas: Illegal seek Ahhh yesss... otherwise known as the subroutine not returning any specific value and the caller expecting an error code, which explains why adding debugging code changed it, running it under the debugger changed it, and just about everything I did changed it, on a random hit or miss basis. My apologies for being too quick on the draw :-( -- ... _._. ._ ._. . _._. ._. ___ .__ ._. . .__. ._ .. ._. Felix Finch: scarecrow repairman & rocket surgeon / [EMAIL PROTECTED] GPG = E987 4493 C860 246C 3B1E 6477 7838 76E9 182E 8151 ITAR license #4933 I've found a solution to Fermat's Last Theorem but I see I've run out of room o ---(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
Re: [GENERAL] bug in 7.4.2, concern unicode and russian content of
On Mon, 2004-06-07 at 12:11, Alexander S. wrote: > There is bug in 7.4.2, concerning unicode and russian letters. For db > in unicode russian data doesn`t order in alphabetical order (rows group > with the same first letter but not in alphabetical order). > SELECT "person" from my_table ORDER BY "person"; > Rows group in such order (approximately): Ð-Ð-Ð-Ð-Ð, but must be : > Ð-Ð-Ð-Ð-Ð. > For english letters all looks fine. For db in koi8r encoding also all > works right. So, I CANNOT use unicode with russian content of db in > postgres. Is it bug or not? What locale was your database initialized with? ---(end of broadcast)--- TIP 6: Have you searched our list archives? http://archives.postgresql.org
[GENERAL] generic insert into table
please CC me, I am on digest - I have the following code from an application that is 'mysql_centric'. I want to make it generic across all databases, if it's possible, especially postgres :-) mysql version: INSERT INTO calendar_setting SET setting='colorEvent',value='#C2DCD5'; There is no data in this table at this time. Isn't this the same as: INSERT INTO calendar_setting( 'colorEvent' ) VALUES ( '#C2DCD5'); would this work on all db's? ---(end of broadcast)--- TIP 2: you can get off all lists at once with the unregister command (send "unregister YourEmailAddressHere" to [EMAIL PROTECTED])
[GENERAL] core dump
We upgraded from 7.2 to 7.4, it looks like everything working, but when I issue a query such as select * from tab (tab has about 2-3 million records), it causes core dump. I tuned some the parameters, it still produce the core. Thanks for any hints. johnl
Re: [GENERAL] generic insert into table
On 7-6-2004 23:29, Dennis Gearon wrote:
please CC me, I am on digest
-
I have the following code from an application that is 'mysql_centric'. I
want to make it generic across all databases, if it's possible,
especially postgres :-)
mysql version:
INSERT INTO calendar_setting SET setting='colorEvent',value='#C2DCD5';
There is no data in this table at this time.
Isn't this the same as:
INSERT INTO calendar_setting( 'colorEvent' ) VALUES ( '#C2DCD5');
would this work on all db's?
Afaik your first example is equal to:
INSERT INTO calendar_setting( setting, value) VALUES ('colorEvent',
'#C2DCD5');
Your first example isn't really SQL-standard and you'd perhaps better
try using SQL-standard stuff as much as possible on MySQL aswell. The
INSERT ... SET-version of INSERT wouldn't be my version to use.
Best regards,
Arjen
---(end of broadcast)---
TIP 4: Don't 'kill -9' the postmaster
Re: [GENERAL] generic insert into table
On Mon, Jun 07, 2004 at 02:29:33PM -0700, Dennis Gearon wrote:
> I have the following code from an application that is 'mysql_centric'. I
> want to make it generic across all databases, if it's possible,
> especially postgres :-)
>
> mysql version:
>INSERT INTO calendar_setting SET setting='colorEvent',value='#C2DCD5';
That would be
INSERT into calendar_setting (setting, value)
VALUES ('colorEvent', '#C2DCD5');
This is the standard syntax, which is not quite the same thing as
saying it will work on all DBs - it will certainly work on both
Postgres and MySQL.
Richard
---(end of broadcast)---
TIP 4: Don't 'kill -9' the postmaster
Re: [GENERAL] core dump
"John Liu" <[EMAIL PROTECTED]> wrote: > We upgraded from 7.2 to 7.4, it looks like everything working, but when I > issue a query such as select * from tab (tab has about 2-3 million records), > it causes core dump. I tuned some the parameters, it still produce the core. It's unlikely that any config settings are causing coredumps. Did you backup and rebuild the database during the upgrade procedure? If not, this could be your problem. You can't run 7.4 on a 7.2 database. Otherwise, you may want to provide more details about the host system and the upgrade procedures you followed. -- Bill Moran Potential Technologies http://www.potentialtech.com ---(end of broadcast)--- TIP 5: Have you checked our extensive FAQ? http://www.postgresql.org/docs/faqs/FAQ.html
Re: [GENERAL] generic insert into table
On Mon, 2004-06-07 at 15:29, Dennis Gearon wrote: > please CC me, I am on digest > - > I have the following code from an application that is 'mysql_centric'. I > want to make it generic across all databases, if it's possible, > especially postgres :-) > > mysql version: > INSERT INTO calendar_setting SET setting='colorEvent',value='#C2DCD5'; For SQL 92, that's not supported syntax. I don't recall if something like it got tossed into the latest SQL 03 standard or not. > There is no data in this table at this time. > Isn't this the same as: > INSERT INTO calendar_setting( 'colorEvent' ) VALUES ( '#C2DCD5'); That's the syntax the SQL 92 spec says to use. > would this work on all db's? Probably not. It's non-standard in the old spec, I don't know about the new one. If it got in the newest spec then it could probably get committed pretty easily. ---(end of broadcast)--- TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
Re: [GENERAL] core dump
On Mon, 2004-06-07 at 15:57, John Liu wrote: > We upgraded from 7.2 to 7.4, it looks like everything working, but > when I issue a query such as select * from tab (tab has about 2-3 > million records), it causes core dump. I tuned some the parameters, it > still produce the core. How odd. Anything else cause it to dump quickly? Does it core if you just run explain select ... (note the lack of an analyze there, as we don't want anything but the planner to run.) Does selecting from another large table cause the same problem, or is this a one table thing? ---(end of broadcast)--- TIP 4: Don't 'kill -9' the postmaster
Re: [GENERAL] core dump
On Mon, 2004-06-07 at 16:19, Bill Moran wrote: > "John Liu" <[EMAIL PROTECTED]> wrote: > > > We upgraded from 7.2 to 7.4, it looks like everything working, but when I > > issue a query such as select * from tab (tab has about 2-3 million records), > > it causes core dump. I tuned some the parameters, it still produce the core. > > It's unlikely that any config settings are causing coredumps. > > Did you backup and rebuild the database during the upgrade procedure? If not, > this could be your problem. You can't run 7.4 on a 7.2 database. 7.4 should refuse to start, without touching the data directory in the old 7.2 directory You should get a version mismatch and a bail out when trying to do so. ---(end of broadcast)--- TIP 8: explain analyze is your friend
[GENERAL] could not bind IPv4 socket: Address already in use
I'm just getting started with postgresql and things are going pretty well. However, I seem to be having trouble connecting to my database via TCP/IP. I'm assuming that my problems are related to the message I get at startup (using "postmaster -D data - i"). The postmaster starts but produces this message: LOG: could not bind IPv4 socket: Address already in use HINT: is another postmaster already running on port 5432. If not, wait a few seconds and retry. Looking into this a bit it seems that the most common issue here is 5432 being claimed by an extra postmaster or another application. However, using "ps -ef" I can confirm that NO other postmasters are running and using "netstat -a" I can confirm that 5432 IS free so I'm at a loss. Oddly, postgres does claim 5432 at startup and releases it at shutdown the way I suspect it should but I still get that message. I came across a discussion at http://www.dbforums.com/archive/index.php/t-968701.html which seems to indicate that the message can be ignored in which case I should look somewhere else for my TCP/IP issues. Has anyone else run into anything like? I'm running Postgresql 7.4.2 on SUSE 8.4. Any thoughts are greatly appreciated. . -- Eric Hillmuth GIS Systems Developer Vermont Agency of Natural Resources 802-241-3616 ---(end of broadcast)--- TIP 5: Have you checked our extensive FAQ? http://www.postgresql.org/docs/faqs/FAQ.html
