Re: [ADMIN] deinstallation - reinstallation on Mac OS 10.4
Thanks a lot for your help! By deleting the pgsql directory I get some steps further. Now I get stuck by a error message saying "postmaster.pid" already exists, when I try to start postmaster. I am not really sure what this means because I think I initiated the database only once, but I guess I have to try a little bit more to solve this problems. Best regards, Christoph Heibl On 21.07.2007, at 04:40, Sibte Abbas wrote: On 7/20/07, Christoph Heibl <[EMAIL PROTECTED]> wrote: Dear experts, I' ve been trying to mirror the harddisk of my old mac via firewire on my new computer (Intel Core Duo, OS 10.4.10) which resulted fairly well expect that my postgreSQL got screwed up. I then tried to install it once more, but this failed. I guess I did not remove all the remaining files before installation and I ended up with this failure: - --- Christoph-Heibls-Computer:~/src/postgresql-8.2.4 Stoffi$ ./configure [] Christoph-Heibls-Computer:~/src/postgresql-8.2.4 Stoffi$ make [] All of PostgreSQL successfully made. Ready to install. Christoph-Heibls-Computer:~/src/postgresql-8.2.4 Stoffi$ make install make -C doc install gzip -d -c ./postgres.tar.gz | ( cd /usr/local/pgsql/doc/html && /usr/bin/tar xf - ) /usr/bin/tar: index.html: Cannot open: File exists /usr/bin/tar: preface.html: Cannot open: File exists /usr/bin/tar: intro-whatis.html: Cannot open: File exists /usr/bin/tar: history.html: Cannot open: File exists /usr/bin/tar: notation.html: Cannot open: File exists /usr/bin/tar: resources.html: Cannot open: File exists [] /usr/bin/tar: bookindex.html: Cannot open: File exists /usr/bin/tar: LEGALNOTICE.html: Cannot open: File exists /usr/bin/tar: stylesheet.css: Cannot open: File exists /usr/bin/tar: Read 2560 bytes from - /usr/bin/tar: Error exit delayed from previous errors make[1]: *** [install] Error 2 make: *** [install] Error 2 - --- The files seem to exist already but I simply do not find them. My questions: Are there deinstallation protocols for Mac? (I was not able to find any...) How can I find and delete these files? Or is it something else that hinders me from installing postgres? I hope to hear from someone who can give me some hints - thanks a lot! Not a Mac guy here, but I think you should try running configure with a different prefix. For example: ./configure --prefix=/usr/local/pgsql-tmp This will avoid conflicts with old left over files (if any). regards, -- Sibte Abbas EnterpriseDB http://www.enterprisedb.com ---(end of broadcast)--- TIP 4: Have you searched our list archives? http://archives.postgresql.org
[ADMIN] problems installing postgresql on Mandriva linux
During installation of postgresql 8.2.4 on Mandriva 2007.1 I get the following
log after typing 'gmake install'
gmake -C doc install
gmake[1]: Entering directory `/home/sg/tmp/postgresql-8.2.4/doc'
gzip -d -c ./postgres.tar.gz | ( cd /usr/local/pgsql/doc/html && /bin/tar xf - )
for file in man1/*.1 man7/*.7 ; do \
/bin/sh ../config/install-sh -c -m 644 $file /usr/local/pgsql/man/$file ||
exit; \
done
cp: setting attributes for `/usr/local/pgsql/man/man1/_inst.4301_': Operace
není podporována {operation/command is not supported}
gmake[1]: *** [install] Error 1
gmake[1]: Leaving directory `/home/sg/tmp/postgresql-8.2.4/doc'
gmake: *** [install] Error 2
Does anyone have an idea what I can do about i? Thanx
---(end of broadcast)---
TIP 2: Don't 'kill -9' the postmaster
Re: [ADMIN] deinstallation - reinstallation on Mac OS 10.4
Christoph Heibl wrote: Thanks a lot for your help! By deleting the pgsql directory I get some steps further. Now I get stuck by a error message saying "postmaster.pid" already exists, when I try to start postmaster. I am not really sure what this means because I think I initiated the database only once, but I guess I have to try a little bit more to solve this problems. The existence of postmaster.pid would indicate that postgresql is either running or was not stopped properly. If it your sure it isn't running then you can delete the .pid file manually. If you are familiar with the terminal then ps aux | grep postgres will list any processes running. If there are any stop postgresql and if the .pid file remains delete it then start postgresql. -- Shane Ambler [EMAIL PROTECTED] Get Sheeky @ http://Sheeky.Biz ---(end of broadcast)--- TIP 2: Don't 'kill -9' the postmaster
Re: [ADMIN] problems installing postgresql on Mandriva linux
<[EMAIL PROTECTED]> writes:
> During installation of postgresql 8.2.4 on Mandriva 2007.1 I get the follow=
> ing log after typing 'gmake install'
> cp: setting attributes for `/usr/local/pgsql/man/man1/_inst.4301_': Operace=
> nen=C3=AD podporov=C3=A1na {operation/command is not supported}
> gmake[1]: *** [install] Error 1
Weird. What type of filesystem are you using --- maybe /usr/local is on
FAT32 or something that doesn't support normal Unix-y file permissions?
regards, tom lane
---(end of broadcast)---
TIP 2: Don't 'kill -9' the postmaster
Re: [ADMIN] "_" in a serach pattern
The only difference is that varchar can have a length limit, text is always unlimited length. There's no significant performance difference between either. For most intents and purposes, they're equal. Forgive me for diversion, but out of curiosity, would it make some difference whether strings of known length are compared or strings of unknown length are compared, like in join condition "using(address)"? Or, is the actual length stored in a separate field and read first so strings of different lengths wouldn't even need to be matched? Is there some reference on this subject other than the source code? Thanks. Ben K. Developer http://benix.tamu.edu ---(end of broadcast)--- TIP 5: don't forget to increase your free space map settings
[ADMIN] Set up a database without backup
Hello everybody. Im using PostgreSQL on Windows XP. I had to format de harddisc, and Im lost databases and tablespaces configuration (1 database and 1 tablespace), I have a copy of directory where was the tablespaces ( but I havent a backup made by pgAdmin ). What do I for set up my database and tablespace ? It could be: creating a new database and tablespace, and after copy files of older tablespace to newer tablespace? Thanks In Advance With Regards Juan. ---(end of broadcast)--- TIP 1: 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: [ADMIN] varchar vs text columns
Andrew Sullivan wrote: On Mon, Jul 23, 2007 at 11:33:54AM -0700, Jessica Richard wrote: What is the difference between varchar and text for a string column? What is the benefit of using each one? Is text better than varchar performance wise? From the manual: Tip: There are no performance differences between these three types, apart from the increased storage size when using the blank-padded type. While character(n) has performance advantages in some other database systems, it has no such advantages in PostgreSQL. In most situations text or character varying should be used instead. Note that varchar(n) will have a performance effect, because on insert or update you have to check to make sure the input doesn't exceed the specified length. See also Peter Koczan's reply in the '"_" in a serach pattern' thread. -- Lew ---(end of broadcast)--- TIP 2: Don't 'kill -9' the postmaster
Re: [ADMIN] deinstallation - reinstallation on Mac OS 10.4
run this in the command line locate postmaster.pid or find / -name "postmaster.pid" -print that should locate any postmaster files and then remove whatever looks like the postmaster.pif file ---(end of broadcast)--- TIP 2: Don't 'kill -9' the postmaster
Re: [ADMIN] Set up a database without backup
2007/7/24, [EMAIL PROTECTED] <[EMAIL PROTECTED]>: Hello everybody. I'm using PostgreSQL on Windows XP. I had to format de harddisc, and I'm lost databases and tablespaces configuration (1 database and 1 tablespace), I have a copy of directory where was the tablespaces ( but I haven't a backup made by pgAdmin ). What do I for set up my database and tablespace ? It could be: creating a new database and tablespace, and after copy files of older tablespace to newer tablespace? Thanks In Advance With Regards Juan. If u have the dirs where the db where initialized you can reinstall the "same" version of postgres on your windows machine and then replace the data dir with your files backup. Alejandro ---(end of broadcast)--- TIP 9: In versions below 8.0, the planner will ignore your desire to choose an index scan if your joining column's datatypes do not match
[ADMIN] Data directory was initialized by PostgreSQL version 8.3
Hi All, Just tried to recompile (what I thought!) was the same version of PG that I already had running, to add in the AdminPack to stop pgAdmin complaining about it being missing. After recompiling from source, with the Admin Pack (did it on a devel box first to make sure I was doing the right thing), I did the following: 1. Shutdown PostgreSQL 2. 'gmake install' the recompiled version (same -prefix = /usr/local/pg-8.2) 3. Restart PostgreSQL Now PostgreSQL complains at me with the following error: 2007-07-25 11:52:05 EST @ []DETAIL: The data directory was initialized by PostgreSQL version 8.3, which is not compatible with this version 8.2.4. As far as I'm aware, 8.3 doesn't exist! The latest version on the postgresql.org website is 8.2.4 I'm assuming the problem is because the PG_VERSION file in the data directory says 8.3, so I'm making a copy of the directory, changing that to 8.2 and see if it will start with that. I can initialize a new data directory and restore last nights backup, but I'd rather not have to loose everything that's happened in the last 4 hours. Any advice on what's going on? Cheers, ~p ***Confidentiality and Privilege Notice*** The material contained in this message is privileged and confidential to the addressee. If you are not the addressee indicated in this message or responsible for delivery of the message to such person, you may not copy or deliver this message to anyone, and you should destroy it and kindly notify the sender by reply email. Information in this message that does not relate to the official business of Weatherbeeta must be treated as neither given nor endorsed by Weatherbeeta. Weatherbeeta, its employees, contractors or associates shall not be liable for direct, indirect or consequential loss arising from transmission of this message or any attachments THINK BEFORE YOU PRINT - Save paper if you don't really need to print this e-mail. ---(end of broadcast)--- TIP 3: Have you checked our extensive FAQ? http://www.postgresql.org/docs/faq
Re: [ADMIN] Data directory was initialized by PostgreSQL version 8.3
> I'm assuming the problem is because the PG_VERSION file in the data > directory says 8.3, so I'm making a copy of the directory, changing that to > 8.2 and see if it will start with that. Well that didn't work! [EMAIL PROTECTED] pgData-8.2]$ pg_ctl -o '-i' start server starting 2007-07-25 12:13:25 EST @ []FATAL: database files are incompatible with server 2007-07-25 12:13:25 EST @ []DETAIL: The database cluster was initialized with PG_CONTROL_VERSION 831, but the server was compiled with PG_CONTROL_VERSION 822. 2007-07-25 12:13:25 EST @ []HINT: It looks like you need to initdb. ***Confidentiality and Privilege Notice*** The material contained in this message is privileged and confidential to the addressee. If you are not the addressee indicated in this message or responsible for delivery of the message to such person, you may not copy or deliver this message to anyone, and you should destroy it and kindly notify the sender by reply email. Information in this message that does not relate to the official business of Weatherbeeta must be treated as neither given nor endorsed by Weatherbeeta. Weatherbeeta, its employees, contractors or associates shall not be liable for direct, indirect or consequential loss arising from transmission of this message or any attachments THINK BEFORE YOU PRINT - Save paper if you don't really need to print this e-mail. ---(end of broadcast)--- TIP 4: Have you searched our list archives? http://archives.postgresql.org
Re: [ADMIN] "_" in a serach pattern
Most database systems can figure out the size (in bytes) of a column rather quickly from offsets within a record. I doubt that postgres is any different. The only difference I can think of is that it might be slower to filter out trailing spaces of a char column before comparing, though the actual string length may be cached somewhere. Semantically, it should be no different. I haven't perused the source code enough to know for sure. Any of the developers that patrol this list can probably answer your questions better, especially the question of matching or not matching strings of different length. Peter Ben Kim wrote: The only difference is that varchar can have a length limit, text is always unlimited length. There's no significant performance difference between either. For most intents and purposes, they're equal. Forgive me for diversion, but out of curiosity, would it make some difference whether strings of known length are compared or strings of unknown length are compared, like in join condition "using(address)"? Or, is the actual length stored in a separate field and read first so strings of different lengths wouldn't even need to be matched? Is there some reference on this subject other than the source code? Thanks. Ben K. Developer http://benix.tamu.edu ---(end of broadcast)--- TIP 6: explain analyze is your friend
Re: [ADMIN] Data directory was initialized by PostgreSQL version 8.3
"Phillip Smith" <[EMAIL PROTECTED]> writes: > Now PostgreSQL complains at me with the following error: > 2007-07-25 11:52:05 EST @ []DETAIL: The data directory was initialized by > PostgreSQL version 8.3, which is not compatible with this version 8.2.4. > As far as I'm aware, 8.3 doesn't exist! You seem to have pulled a development snapshot from someplace ... > I'm assuming the problem is because the PG_VERSION file in the data > directory says 8.3, so I'm making a copy of the directory, changing that to > 8.2 and see if it will start with that. There is exactly 0 chance that that will work. The PG_VERSION test is there to save you from worse and more obscure failures involving incompatible system catalog layouts. regards, tom lane ---(end of broadcast)--- TIP 7: You can help support the PostgreSQL project by donating at http://www.postgresql.org/about/donate
Re: [ADMIN] Data directory was initialized by PostgreSQL version 8.3
"Phillip Smith" <[EMAIL PROTECTED]> writes: >> Now PostgreSQL complains at me with the following error: >> 2007-07-25 11:52:05 EST @ []DETAIL: The data directory was initialized by >> PostgreSQL version 8.3, which is not compatible with this version 8.2.4. >> As far as I'm aware, 8.3 doesn't exist! > You seem to have pulled a development snapshot from someplace ... Thanks Tom... I recall you giving me a patch for an error I was having when I first upgraded to 8.2 but I can't for the life of me remember the error. Is it worth me trying to fix this stuff up on my behalf? Or should I just go back to last night's backup and recreate this morning's transactions? ***Confidentiality and Privilege Notice*** The material contained in this message is privileged and confidential to the addressee. If you are not the addressee indicated in this message or responsible for delivery of the message to such person, you may not copy or deliver this message to anyone, and you should destroy it and kindly notify the sender by reply email. Information in this message that does not relate to the official business of Weatherbeeta must be treated as neither given nor endorsed by Weatherbeeta. Weatherbeeta, its employees, contractors or associates shall not be liable for direct, indirect or consequential loss arising from transmission of this message or any attachments THINK BEFORE YOU PRINT - Save paper if you don't really need to print this e-mail. ---(end of broadcast)--- TIP 1: 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: [ADMIN] Data directory was initialized by PostgreSQL version 8.3
"Phillip Smith" <[EMAIL PROTECTED]> writes: >>> 2007-07-25 11:52:05 EST @ []DETAIL: The data directory was initialized >>> by >>> PostgreSQL version 8.3, which is not compatible with this version 8.2.4. > Is it worth me trying to fix this stuff up on my behalf? Or should I just go > back to last night's backup and recreate this morning's transactions? If you can reinstall the server software you had yesterday, do that and do a pg_dumpall, then install 8.2.4, initdb, reload from dump. regards, tom lane ---(end of broadcast)--- TIP 9: In versions below 8.0, the planner will ignore your desire to choose an index scan if your joining column's datatypes do not match
Re: [ADMIN] Installing PgAdmin package on Linux
HI Ashish, Try to download the source for Linux installation from the PgAdmin site. untar and try to complile using ./configure make and make install steps. Just test what happens. I too do not see any options give somewhere. you can also go through Readme file give with the source binary. I am not on linux system these days or else I could have tried and told you. - Vishal From: "Ashish Karalkar" <[EMAIL PROTECTED]> To: Subject: [ADMIN] Installing PgAdmin package on Linux Date: Tue, 24 Jul 2007 11:54:33 +0530 Hello All, I am having PostgreSQL server 8.2.0 running on Redhat Linux . I want to install PgAdmin GUI on the Linux Server. can anybody please guide me to the appropriate documantation and the prerequisite required for the same . Thanks In Adavnce With Reagrds Ashish... _ Don't get caught with egg on your face. Play Chicktionary! http://club.live.com/chicktionary.aspx?icid=chick_hotmailtextlink2 ---(end of broadcast)--- TIP 7: You can help support the PostgreSQL project by donating at http://www.postgresql.org/about/donate
