[GENERAL] phpPgAdmin 6 on a MAC (High Sierra)
Apple has added PostgreSQL support to php in High Sierra. PhpPgAdmin seems to have died at Version 5.1 and it does not play nice with php 7.x. There is a fork called phpPgAdmin 6. I have been able to get the interface up but selecting a database results in an error. My php-foo is weak...has anyone been to get phpPgAdmin working on a Mac running High Sierra? Thanks for any info... Trapped in Steve Jobs Reality Distortion Field -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
Re: [GENERAL] Strange Errors...
> On Feb 22, 2017, at 10:08 AM, Jerry LeVan wrote: > >> >> On Feb 22, 2017, at 9:49 AM, Adrian Klaver wrote: >> >> On 02/22/2017 07:32 AM, Jerry LeVan wrote: >>> >>>> On Feb 22, 2017, at 9:20 AM, Adrian Klaver >>>> wrote: >>>> >>>> On 02/22/2017 07:09 AM, Jerry LeVan wrote: >>>>> Sorry I accidentally posted this to pgsql-general-owners earlier today… >>>>> >>>>> How can this happen ( from the postgresql.log file) >>>>> >>>>> LOG: statement: select * from knives where manufacturer=‘Boker’ >>>>> ERROR: column "‘boker’" does not exist at character 41 >>>>> >>>>> Some background: >>>>> I am trying to move from 32 bit apps to 64 bit apps. I still >>>>> have a couple of 32 bit apps that talk to postgresql. >>>>> >>>>> env: >>>>> MacOS Sierra 10.12.3 >>>>> >>>>> postgresql 9.6.2 compiled as a 64 bit program. I also >>>>> compiled it as a 32 bit program and glued the 64 bit >>>>> and 32 bit libpq libraries together and replaced the >>>>> installed 64 bit libpq library with the fat version. >>>>> >>>>> python 2.7.10 Apple’s version >>>>> >>>>> psycopg2 2.6.1 >>>>> >>>>> wxpython '3.0.3.0.b20160914’ installed from the wxpython.org site. >>>>> >>>>> My main interaction with my database is a wxpython app. I type >>>>> sql into a text window and can send the contents of the window >>>>> or the selection or the line containing the cursor to postgresql >>>>> >>>>> It appears that every single quote ( ‘ ) gets translated somehow to >>>> >>>> No: >>>> >>>> test=# select ‘Boker’; >>>> ERROR: column "‘boker’" does not exist >>>> LINE 1: select ‘Boker’; >>>> >>>> test=# select 'Boker'; >>>> ?column? >>>> -- >>>> Boker >>>> (1 row) >>>> >>>> It is because they are ‘ ’ not ' '. >>>> >>>> So you need to find out what is causing your program to introduce ‘ ’. >>> >>> The mail program is displaying the straight quote as a curly quote… >>> In the terminal program I see a straight quote. >>> >>> Perhaps wxpython is somehow confusing things… tain’t clear on >>> how to test. >> >> I have seen this issue when I cut and pasted data from word >> processing/spreadsheet programs and not paid attention to the fact they have >> settings that convert ' --> ’ and '' --> ‘‘ ’’. >> >>> >>>> >> > I think you may be on to something….If I how down the straight quote in the > text window for a few seconds I can see a > ripple of changes to a different character when I release the key. If I zoom > the terminal window displaying > the log file the quote is clearly not the ‘straight’ quote. >>>> >>>> -- >>>> Adrian Klaver >>>> adrian.kla...@aklaver.com >>> >>> >> >> >> -- >> Adrian Klaver >> adrian.kla...@aklaver.com There is a setting in the Mac System Preferences that will allow you to turn off smart quotes. I did this and the program is acting properly once more :) Thanks for the tip. Jerry -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
Re: [GENERAL] Strange Errors...
> On Feb 22, 2017, at 9:49 AM, Adrian Klaver wrote: > > On 02/22/2017 07:32 AM, Jerry LeVan wrote: >> >>> On Feb 22, 2017, at 9:20 AM, Adrian Klaver >>> wrote: >>> >>> On 02/22/2017 07:09 AM, Jerry LeVan wrote: >>>> Sorry I accidentally posted this to pgsql-general-owners earlier today… >>>> >>>> How can this happen ( from the postgresql.log file) >>>> >>>> LOG: statement: select * from knives where manufacturer=‘Boker’ >>>> ERROR: column "‘boker’" does not exist at character 41 >>>> >>>> Some background: >>>> I am trying to move from 32 bit apps to 64 bit apps. I still >>>> have a couple of 32 bit apps that talk to postgresql. >>>> >>>> env: >>>> MacOS Sierra 10.12.3 >>>> >>>> postgresql 9.6.2 compiled as a 64 bit program. I also >>>> compiled it as a 32 bit program and glued the 64 bit >>>> and 32 bit libpq libraries together and replaced the >>>> installed 64 bit libpq library with the fat version. >>>> >>>> python 2.7.10 Apple’s version >>>> >>>> psycopg2 2.6.1 >>>> >>>> wxpython '3.0.3.0.b20160914’ installed from the wxpython.org site. >>>> >>>> My main interaction with my database is a wxpython app. I type >>>> sql into a text window and can send the contents of the window >>>> or the selection or the line containing the cursor to postgresql >>>> >>>> It appears that every single quote ( ‘ ) gets translated somehow to >>> >>> No: >>> >>> test=# select ‘Boker’; >>> ERROR: column "‘boker’" does not exist >>> LINE 1: select ‘Boker’; >>> >>> test=# select 'Boker'; >>> ?column? >>> -- >>> Boker >>> (1 row) >>> >>> It is because they are ‘ ’ not ' '. >>> >>> So you need to find out what is causing your program to introduce ‘ ’. >> >> The mail program is displaying the straight quote as a curly quote… >> In the terminal program I see a straight quote. >> >> Perhaps wxpython is somehow confusing things… tain’t clear on >> how to test. > > I have seen this issue when I cut and pasted data from word > processing/spreadsheet programs and not paid attention to the fact they have > settings that convert ' --> ’ and '' --> ‘‘ ’’. > >> >>> > I think you may be on to something….If I how down the straight quote in the text window for a few seconds I can see a ripple of changes to a different character when I release the key. If I zoom the terminal window displaying the log file the quote is clearly not the ‘straight’ quote. >>> >>> -- >>> Adrian Klaver >>> adrian.kla...@aklaver.com >> >> > > > -- > Adrian Klaver > adrian.kla...@aklaver.com -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
Re: [GENERAL] Strange Errors...
> On Feb 22, 2017, at 9:20 AM, Adrian Klaver wrote: > > On 02/22/2017 07:09 AM, Jerry LeVan wrote: >> Sorry I accidentally posted this to pgsql-general-owners earlier today… >> >> How can this happen ( from the postgresql.log file) >> >> LOG: statement: select * from knives where manufacturer=‘Boker’ >> ERROR: column "‘boker’" does not exist at character 41 >> >> Some background: >> I am trying to move from 32 bit apps to 64 bit apps. I still >> have a couple of 32 bit apps that talk to postgresql. >> >> env: >> MacOS Sierra 10.12.3 >> >> postgresql 9.6.2 compiled as a 64 bit program. I also >> compiled it as a 32 bit program and glued the 64 bit >> and 32 bit libpq libraries together and replaced the >> installed 64 bit libpq library with the fat version. >> >> python 2.7.10 Apple’s version >> >> psycopg2 2.6.1 >> >> wxpython '3.0.3.0.b20160914’ installed from the wxpython.org site. >> >> My main interaction with my database is a wxpython app. I type >> sql into a text window and can send the contents of the window >> or the selection or the line containing the cursor to postgresql >> >> It appears that every single quote ( ‘ ) gets translated somehow to > > No: > > test=# select ‘Boker’; > ERROR: column "‘boker’" does not exist > LINE 1: select ‘Boker’; > > test=# select 'Boker'; > ?column? > -- > Boker > (1 row) > > It is because they are ‘ ’ not ' '. > > So you need to find out what is causing your program to introduce ‘ ’. The mail program is displaying the straight quote as a curly quote… In the terminal program I see a straight quote. Perhaps wxpython is somehow confusing things… tain’t clear on how to test. > >> a double quote ( “ ). SQL statements that do not use quotes return >> properly and I can display the results in a grid. >> >> I have modified one of the test programs in the psycopg2 distribution >> that sends the selection shown in the log statement and it works >> properly. i.e. I can send the select statement and retrieve the results >> from a the psycopg2 python program. >> >> I can run basically the same wxpthon program on my fedora system without >> any problems (talking to the mac ). >> >> Any suggestions would be appreciated. >> >> Jerry >> > > > -- > Adrian Klaver > adrian.kla...@aklaver.com -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
[GENERAL] Strange Errors...
Sorry I accidentally posted this to pgsql-general-owners earlier today… How can this happen ( from the postgresql.log file) LOG: statement: select * from knives where manufacturer=‘Boker’ ERROR: column "‘boker’" does not exist at character 41 Some background: I am trying to move from 32 bit apps to 64 bit apps. I still have a couple of 32 bit apps that talk to postgresql. env: MacOS Sierra 10.12.3 postgresql 9.6.2 compiled as a 64 bit program. I also compiled it as a 32 bit program and glued the 64 bit and 32 bit libpq libraries together and replaced the installed 64 bit libpq library with the fat version. python 2.7.10 Apple’s version psycopg2 2.6.1 wxpython '3.0.3.0.b20160914’ installed from the wxpython.org site. My main interaction with my database is a wxpython app. I type sql into a text window and can send the contents of the window or the selection or the line containing the cursor to postgresql It appears that every single quote ( ‘ ) gets translated somehow to a double quote ( “ ). SQL statements that do not use quotes return properly and I can display the results in a grid. I have modified one of the test programs in the psycopg2 distribution that sends the selection shown in the log statement and it works properly. i.e. I can send the select statement and retrieve the results from a the psycopg2 python program. I can run basically the same wxpthon program on my fedora system without any problems (talking to the mac ). Any suggestions would be appreciated. Jerry -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
[GENERAL] 64 and 32 bit libpq
Hello, I am trying to upgrade my postgresql ‘stuff’ to 64 bits from 32 bits. I am running MaxOS Sierra. I have built the 64 bit version of the server and have loaded my database into the new server ( 9.6.2 ). Everything seems to be working. I have some legacy apps that are 32 bit and talk to the server via libpq.dylib. They no longer work with a complaint about not finding a libpq with the right architecture. Can I go back and do a 32 bit rebuild of everything and then take the 32 bit libpq and the 64 bit libpq and use lipo to glue them together and create a ‘fat’ libpq and replace the installed libpq? Is this a safe thing to do? Thanks Jerry -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
Re: [GENERAL] configure can't find libcrypto on MacOS Sierra for pg 9.6.2
Sigh, I will try to build without OpenSSL… My database is seventeen years old, I don’t even remember which Postgresql I started out with... Jerry > On Feb 12, 2017, at 10:53 AM, Tom Lane wrote: > > Jerry LeVan writes: >> Hello, I am trying to build pg 9.6.2 on my MacOS Sierra but >> configure is being balky > > Hmm, I'm not really sure why it's failing at that step --- it gets past > that for me. Possibly looking into config.log to see if there's a more > detailed error report would be illuminating. However, trying to build > against Apple's openssl libraries is a lost cause anyway, because they > removed the header files in Sierra. So it will fail when it gets to > header file checks; where it stops for me is > > checking for openssl/ssl.h... no > configure: error: header file is required for OpenSSL > > AFAIK the only way forward is to install a complete OpenSSL installation > from source, or using MacPorts or brew or other tool-of-choice. > > Apple would really like people to start using their SSL infrastructure. > That handwriting has been on the wall for years, but nobody's gotten > around to writing the necessary interface logic for Postgres. > > regards, tom lane -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
[GENERAL] configure can't find libcrypto on MacOS Sierra for pg 9.6.2
Hello, I am trying to build pg 9.6.2 on my MacOS Sierra but configure is being balky configure:9494: checking for CRYPTO_new_ex_data in -lcrypto configure:9519: gcc -o conftest -Wall -Wmissing-prototypes -Wpointer-arith -Wdeclaration-after-statement -Wendif-labels -Wmissing-for mat-attribute -Wformat-security -fno-strict-aliasing -fwrapv -Wno-unused-command-line-argument -O2 conftest.c -lcrypto -lz -ledi t -lm >&5 ld: library not found for -lcrypto clang: error: linker command failed with exit code 1 (use -v to see invocation) configure:9519: $? = 1 but libcrypto is present: eagle:Desktop postgres$ ls -al /usr/lib/libcrypto* -rwxr-xr-x 1 root wheel 2043536 Dec 10 04:53 /usr/lib/libcrypto.0.9.7.dylib -rwxr-xr-x 1 root wheel 2681408 Dec 10 04:53 /usr/lib/libcrypto.0.9.8.dylib -rw-r--r-- 1 root wheel 4209728 Dec 10 04:53 /usr/lib/libcrypto.35.dylib lrwxr-xr-x 1 root wheel 21 Sep 24 13:20 /usr/lib/libcrypto.dylib -> libcrypto.0.9.8.dylib The config.log file for 9.3.2 passes the test. And for the 9.3.2 image: eagle:Desktop postgres$ otool -L /usr/local/bin/postgres /usr/local/bin/postgres: /usr/lib/libssl.0.9.8.dylib (compatibility version 0.9.8, current version 50.0.0) /usr/lib/libcrypto.0.9.8.dylib (compatibility version 0.9.8, current version 50.0.0) /usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 1197.1.1) eagle:Desktop postgres$ Any suggestions? Thanks Jerry -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
[GENERAL] Broken after upgrade
> I am left today, after an upgrade I think (Fedora 23 --> 24) with a > broken postgresql. > > It used to work very well. The service is started with the systemd > unit file. I have now this error: > > - > postgres@thetradinghall 筐､筐､ systemd/system % > /usr/libexec/postgresql-ctl start -D /db/pgsql/data -s -w -t 270 > FATAL: 22023: database files are incompatible with server > DETAIL: The data directory was initialized by PostgreSQL version 9.4, > which is not compatible with this version 9.5.3. > --- > > Googling it gave me some entries, but I couldn't find any clear > explanation and how to solve. It seems I need to initiate a new > database, but thereafter is not clear (how to use my old data and conf > files pg_hba and pg_ident). > > Thank you for hints/links how to solve this issue. > — I did this also ;( You might have to remove the 9.5.3 postgresql rpms and install the 9.4 postgresql rpms. You can then do a pg_dumpall to get a portable dump of your database ( if it is not too large ). You can then reinstall the 9.5.3 rpms and create a new database with the dump. Fortunately I had a clone of my db on another machine so I was able to copy the pg_dumpall from the other machine and recreate my database. Jerry -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
Re: [GENERAL] Yosemite (OSX 10.0) problems with Postgresql
On Oct 20, 2014, at 7:45 AM, Michael Paquier wrote: > > > On Mon, Oct 20, 2014 at 9:26 PM, Jerry Levan wrote: > 1) The upgrade evidently *deletes* directories pg_tblspc, pg_twophase, and > pg_stat_tmp from >the postgresql data directory. Google said to recreate the missing > directories and indeed >Postgresql then was able to start. > That's a good way to corrupt your data if using 2PC and tablespaces. (Be sure > to take a backup before the upgrade). It might be the case that the deletion would occur if the directories were empty (As they are on all of my systems ). Perhaps we will find out in a couple of days ;( > > 2) SystemStarter is no longer available. Gulp… I am not a very good plist > creator. > Is there a fairly generic plist I can edit to specify my locations of the > software bits so I can have postgresql started at boot time? > That's not surprising, this feature is deprecated in Mavericks. And launched? Yeah, launchd is still around, that is why I need a .plist file so I can start Postgresql at boot time. > -- > Michael Jerry -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
[GENERAL] Yosemite (OSX 10.0) problems with Postgresql
I just upgraded one of my Mac computers to Yosemite and am having a small problem. 1) The upgrade evidently *deletes* directories pg_tblspc, pg_twophase, and pg_stat_tmp from the postgresql data directory. Google said to recreate the missing directories and indeed Postgresql then was able to start. 2) SystemStarter is no longer available. Gulp… I am not a very good plist creator. Is there a fairly generic plist I can edit to specify my locations of the software bits so I can have postgresql started at boot time? Thanks, Jerry -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
Re: [GENERAL] Thousands of errors...what happened?
On Mar 24, 2014, at 11:30 AM, Sergey Konoplev wrote: > On Mon, Mar 24, 2014 at 9:14 AM, Jerry Levan wrote: >> ERROR: could not seek to end of file "global/12292": Too many open files >> LOG: out of file descriptors: Too many open files; release and retry > [...] >> Any idea what the problem could have been? > > Well, it tells for itself. It is out of file descriptors. Assuming you > are on Linux, the ways to fix it (to increase the limit) are described > by the link [1]. Chose one that suits you better. This is on the latest MacOSX and generally I have very few apps open. This is the first time this has happened in over fourteen years of using Postgresql. Jerry -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
[GENERAL] Thousands of errors...what happened?
The other day I attempted to connect to my 9.3.2 postgresql data base and my connection attempts kept failing. I found about 10 lines in the log file that looked like: ERROR: could not seek to end of file "global/12292": Too many open files LOG: out of file descriptors: Too many open files; release and retry ERROR: could not seek to end of file "global/12292": Too many open files LOG: out of file descriptors: Too many open files; release and retry ERROR: could not seek to end of file "global/12292": Too many open files LOG: out of file descriptors: Too many open files; release and retry ERROR: could not seek to end of file "global/12292": Too many open files LOG: out of file descriptors: Too many open files; release and retry ERROR: could not seek to end of file "global/12292": Too many open files LOG: out of file descriptors: Too many open files; release and retry ERROR: could not seek to end of file "global/12292": Too many open files LOG: out of file descriptors: Too many open files; release and retry ERROR: could not seek to end of file "global/12292": Too many open files LOG: out of file descriptors: Too many open files; release and retry ERROR: could not seek to end of file "global/12292": Too many open files LOG: out of file descriptors: Too many open files; release and retry ERROR: could not seek to end of file "global/12292": Too many open files LOG: out of file descriptors: Too many open files; release and retry ERROR: could not seek to end of file "global/12292": Too many open files LOG: database system was interrupted; last known up at 2014-03-01 07:49:58 CST LOG: database system was not properly shut down; automatic recovery in progress LOG: record with zero length at 0/1BD6680 LOG: redo is not required LOG: database system is ready to accept connections LOG: autovacuum launcher started LOG: database system was interrupted; last known up at 2014-03-15 07:35:29 CDT LOG: database system was not properly shut down; automatic recovery in progress LOG: record with zero length at 0/1BE41F4 LOG: redo is not required LOG: database system is ready to accept connections LOG: autovacuum launcher started I could not stop the postgresql server so I had to reboot the system (: I am the only user of the db and I use the rascal spareinly. Any idea what the problem could have been? Jerry -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
[GENERAL] In a moment of madness I destroyed...
Today I updated my fedora machine from f19 to f20 without taking a data dump. When ‘fedup’ finished my 9.2.x binaries were updated to 9.3.x and postgresql can no longer start… I have all of the tables on another machine ( a mac running 9.1.x postgresql) so no important data was lost. ( My db consists primarily of all of my financial transactions for the last 14 years and some miscellaneous tables for stashing other interesting information.) Any suggestions for recovery would be appreciated. Would a text pg_dumpall from the mac be portable to the 9.3.x version on the PAE kerneled fedora box? It looks like I would at a minimum move the current pgsql directory and then do the initdb and create user stuff… I guess I could then possibly use the dblink stuff to suck the tables over one at a time… Thanks Dazed and Confused Jerry -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
[GENERAL] Strange Connection Problem….
Hi, I recently modified one of my Fedora boxes by changing it's name and ip. I also disabled the internal wifi ( connection speed was dropping to 1 mb/sec ) and configured a USB wifi stick ( wow 270~300 mb/sec ). As I checked out the refurbed box networking was ok and I was able to connect to Postgresql using pgsql and some of my personal apps. However I could not connect to Postgresql from my other machines. I tried ssh from another machine to the modified machine and of course ssh complained about have a bad key ( had renamed the machine to a machine that I had given away recently and the key to the old machine was still present.) After I fixed the ssh problem I *was* able to connect to Postgresql on the refurbed machine. Do the postgresql libraries silently check to see if there is a ssh 'footprint' available for a target machine and reject the connection attempt if they do not match? Jerry -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
Re: [GENERAL] Pokey Fedora Updates for Postgresql?
On Feb 17, 2012, at 4:58 PM, Tom Lane wrote: > Jerry Levan writes: >> On Feb 17, 2012, at 4:21 PM, Tom Lane wrote: >>> I beg your pardon? > >> Sorry, they do not appear in *my* 'yum update' or yumex or the software >> update program. > > Huh. Something broken on your end, but what? The only thing that looks > funny to me in your output is > >> [jerry@bigbox ~]$ yum check-update >> Loaded plugins: fastestmirror, presto, refresh-packagekit > ^ > > That's not a standard plugin (leastwise I don't see it when I run yum) > so I'm wondering if it's pointing you to a dysfunctional mirror. Try > disabling it. > > FWIW, as of today I see this on my F16 machine: > > [tgl@rh3 ~]$ sudo yum check-update > Loaded plugins: auto-update-debuginfo, langpacks, presto, refresh-packagekit > updates/metalink | 16 kB 00:00 > > updates | 4.5 kB 00:00 > > updates/primary_db | 5.0 MB 00:02 > > updates/group_gz | 431 kB 00:00 > > updates-debuginfo/metalink | 13 kB 00:00 > > updates-debuginfo| 3.1 kB 00:00 > > updates-debuginfo/primary_db | 391 kB 00:00 > > > The fact that your "updates/primary_db" is smaller than mine seems > pretty suspicious. I wonder whether you've been seeing any Fedora > updates at all lately? Maybe everything you've updated has been coming > from those non-Fedora repos. > > regards, tom lane Sigh, "Whenever the unlikely solutions are rejected then all that are left are the probable." In fedora 15 I had been using Devrim's repo and had 'excluded' postgresql in the fedora and fedora update repositories. When fedora 16 came out I removed the exclusion from the fedora repo but NOT the update repo. (and I disabled the pgdg repo). Sorry for all the noise… Jerry -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
Re: [GENERAL] Pokey Fedora Updates for Postgresql?
On Feb 17, 2012, at 4:21 PM, Tom Lane wrote: > Jerry Levan writes: >> Seems like Postgresql 9.1.2 has been out for a while but it has >> not appeared in the updates for Fedora 16. > > I beg your pardon? Sorry, they do not appear in *my* 'yum update' or yumex or the software update program. I have been getting regular updates for many packages. ( I check daily ). I have the 9.1.1 rpms installed… [jerry@bigbox ~]$ rpm -qa | grep postgres postgresql-contrib-9.1.1-1.fc16.i686 postgresql-plpython-9.1.1-1.fc16.i686 postgresql-devel-9.1.1-1.fc16.i686 postgresql-server-9.1.1-1.fc16.i686 postgresql-pltcl-9.1.1-1.fc16.i686 postgresql-upgrade-9.1.1-1.fc16.i686 postgresql-docs-9.1.1-1.fc16.i686 postgresql-libs-9.1.1-1.fc16.i686 postgresql-9.1.1-1.fc16.i686 [jerry@bigbox ~]$ yum check-update Loaded plugins: fastestmirror, presto, refresh-packagekit Loading mirror speeds from cached hostfile updates/metalink | 16 kB 00:00 * fedora: mirror.vcu.edu * rpmfusion-free: mirror.liberty.edu * rpmfusion-free-updates: mirror.liberty.edu * rpmfusion-nonfree: mirror.liberty.edu * rpmfusion-nonfree-updates: mirror.liberty.edu * updates: mirror.vcu.edu Dropbox | 951 B 00:00 adobe-linux-i386 | 951 B 00:00 adobe-linux-i386/primary | 11 kB 00:00 adobe-linux-i386 17/17 rpmfusion-free-updates | 3.3 kB 00:00 rpmfusion-nonfree-updates| 3.3 kB 00:00 updates | 4.5 kB 00:00 updates/primary_db | 3.9 MB 00:19 [jerry@bigbox ~]$ I guess there is a problem on my end, tain't clear to me what the problem could be… I must be holding it wrong... Jerry > > https://admin.fedoraproject.org/updates/FEDORA-2012-0346/postgresql-9.1.2-2.fc16 > https://admin.fedoraproject.org/updates/FEDORA-2011-16803/postgresql-9.1.2-1.fc16 > > regards, tom lane -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
[GENERAL] Pokey Fedora Updates for Postgresql?
I guess I am feeling a bit cranky today :(… Seems like Postgresql 9.1.2 has been out for a while but it has not appeared in the updates for Fedora 16. Today I cruised koji.fedoraproject.org and noticed that a set of rpms appear to been built by , ummm, 'tgl' back in early January. Does anyone know how to kickstart the process of getting the latest version pushed out to the repos? Thanks, Jerry ( Yes I know about Devrim's repository..) -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
Re: [GENERAL] Client SQL Tool
On Nov 14, 2011, at 5:33 PM, pgsql-general-ow...@postgresql.org wrote: > Date: Mon, 14 Nov 2011 16:01:16 +0100 > From: > To: > Subject: Client SQL Tool > Message-ID: <2D9339CD594D4A68B51E9D0B3AF134F4@neuromancer> > > Hi all, > > Iâ•˙ve started a new codeplex project that could be interesting for you. > Itâ•˙s a simple SQL client for postgreSQL databases. > You can found it here : http://postgresqlclient.codeplex.com/ > > Iâ•˙ve started with this project, because i want to improve my WPF skills and > create something useful for the postgresql environment. > So, take a look and give me feedback if you like. > > Thanks > Björn If you are looking for enhancement ideas, you might take a peek at my website http://homepage.mac.com/levanj ( while it still exists ). I have several postgresql clients that have a similar layout but most are written in scripting languages ( wxpython, tcl/tk ) and one written in Cocoa ( which may or may not still work ). They can typically do stuff like import/export large objects or bytea objects, display pictures and support libraries of sql code fragments. Maybe you can find some good use for the algorithms in the code :) It was fun writing my own tools… Have fun on you voyage :) Jerry -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
[GENERAL] Re: [GENERAL] Re: [GENERAL] Need Help Installing Dblink…(Desperately…)
On Nov 12, 2011, at 5:49 PM, Tom Lane wrote: > Jerry Levan writes: >> On Nov 12, 2011, at 3:34 PM, Scott Mead wrote: >>> The Makefile should be including the global did you try a 'make >>> install' ? > >> I went back and did the make install from the dblink directory it installed >> stuff in the share directory but invoking dblink functions failed with >> an unknown definition. I invoked the create extension command but it >> did no good... > > Vague handwaving like that is an excellent way to guarantee that nobody > can help you, because we can't figure out what you did wrong (or, maybe, > what the code did wrong) based on this. We need to see exactly what > commands you gave and what results you got. Please read > http://wiki.postgresql.org/wiki/Guide_to_reporting_problems > > (In general, though, in PG 9.1 you do not source contrib SQL scripts > directly. CREATE EXTENSION is the way to install a contrib module into > a database.) > > regards, tom lane You are, as usual, correct in your criticism. My only excuse is that I hit the panic button when things got out of control ;( My first bad step was moving the source folder after I built the main database server, clients, etc and then trying to build the dblink extension. It appears that some *.h files had been linked via absolute paths causing the compilation of the dblink package build to fail. Moving the source folder back to its original location fixed that problem. The second difficulty was that I did not understand about extensions and how to install and enable the rascals. After I built the documentation and did some reading about extensions I was able to (I hope) properly install the dblink package. My sql codes that use dblink now act the same in 9.1.1 as they did in 9.0.x I will find out for sure tomorrow when I upgrade two more macs… Jerry -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
[GENERAL] Re: [GENERAL] Need Help Installing Dblink…(Desperately…)
On Nov 12, 2011, at 3:34 PM, Scott Mead wrote: > > On Sat, Nov 12, 2011 at 1:02 PM, Jerry Levan wrote: > I think I have somehow botched my installation of 9.1.1 on Mac OSX 10.7.2 > > I have a mac running 9.1.1. > > I then built dblink from the contrib directory and I did not > see an install option in the make file. > > The Makefile should be including the global did you try a 'make install' > ? > > I went back and did the make install from the dblink directory it installed stuff in the share directory but invoking dblink functions failed with an unknown definition. I invoked the create extension command but it did no good... I went back to a previous version and loaded the older dblink.sql file and it now appears to be working…at least the dblink function calls that my sql uses is appearently working. > I tried copying the dblink.so file to the postgresql library directory > but i cannot figure out how to install the definitions.. > > google: > > http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/contrib/dblink/Attic/README.dblink?rev=1.12.4.1 > This is pre-extension stuff… > > Any clues would be helpful. > > Thanks > > Jerry > > -- > Sent via pgsql-general mailing list (pgsql-general@postgresql.org) > To make changes to your subscription: > http://www.postgresql.org/mailpref/pgsql-general > -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
[GENERAL] Need Help Installing Dblink…(Desperately…)
I think I have somehow botched my installation of 9.1.1 on Mac OSX 10.7.2 I have a mac running 9.1.1. I then built dblink from the contrib directory and I did not see an install option in the make file. I tried copying the dblink.so file to the postgresql library directory but i cannot figure out how to install the definitions.. Any clues would be helpful. Thanks Jerry -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
[GENERAL] dblink build problem…must be a lesson here...
Hi, I compiled pg 9.1.1 on my Mac OX 10.7.2 this afternoon and when I attempted to build dblink I got: eagle:dblink postgres$ export CC="gcc -arch i386" eagle:dblink postgres$ make gcc -arch i386 -O2 -Wall -Wmissing-prototypes -Wpointer-arith -Wdeclaration-after-statement -Wendif-labels -Wformat-security -fno-strict-aliasing -fwrapv -I../../src/interfaces/libpq -I. -I. -I../../src/include -c -o dblink.o dblink.c In file included from ../../src/include/postgres.h:48, from dblink.c:33: ../../src/include/utils/elog.h:69:28: error: utils/errcodes.h: No such file or directory dblink.c:62:28: error: utils/fmgroids.h: No such file or directory The files errcodes.h and fmgrouds.h appear to be links to nowhere… I scratched my head for a while. I finally recalled that after I ran config and built postgresql I moved the source folder to a different location. This evidently screws up some of the links…not good. When I moved the folder back to its original location dblink.so built with no problems. Be careful out there :) It has been a long time since I have messed with installing dblink. Do I need to install the sql again? If so where and how do I reinstall the sql interfaces… T'aint clear to me when dblink needs to be reinstalled. Jerry -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
Re: [GENERAL] Fedora 16 note...
On Nov 10, 2011, at 9:56 PM, Craig Ringer wrote: > On 11/10/2011 11:10 PM, Jerry Levan wrote: >> I upgraded to Fedora 16 yesterday… >> >> I thought I might have lost my 12 year old db when the system came up >> and I noticed the 9.1 had overwrote the old binaries. > > ... of course, you keep regular backups so you weren't too worried anyway > right? > Not that I am paranoid or anything but I keep manually maintained clones on three other machines that are backed up via time machine to my NAS and I superduper the macs to separate disks. I also semi-periodically rsync many directories on the Fedora box to a separate disk. Dblink makes the manually cloning of the tables an easy task. I have written a bunch of tools to access postgresql, sorta like a PgAdmin light ( http://homepage.mac.com/levanj ) >> Then I read about pg_upgrade stuff and it worked! > > Good to hear. I tend to dump and reload between versions as I have fairly > small data, but it's good to hear people getting successful use out of > pg_upgrade. > >> I found that postgresql would not start at boot time until >> I did: >> >> systemctl enable postgresql.service > > That's Fedora policy: don't start a service unless the user asks for it to be > started. This is the first time I have had to manually enable a service like postgresql and httpd since Fedora 4. I guess this is mostly from the systemd take over... > > -- > Craig Ringer -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
[GENERAL] Fedora 16 note...
I upgraded to Fedora 16 yesterday… I thought I might have lost my 12 year old db when the system came up and I noticed the 9.1 had overwrote the old binaries. Then I read about pg_upgrade stuff and it worked! I found that postgresql would not start at boot time until I did: systemctl enable postgresql.service Jerry -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
[GENERAL] How can I merge two tables?
Hi, I have tables on my various computers that looks like: Table "public.registrations" Column | Type | Modifiers | Storage | Description --+--+---+--+- software | text | | extended | id | text | | extended | value| text | | extended | location | text | | extended | Indexes: "registrations_software_idx" btree (software) CLUSTER Has OIDs: yes I keep registration numbers for software and login/passwords for various organizations, etc… As time goes by the tables on the various computers get out of sync. Is there an elegant way I can get all of the differences (uniquely) merged into a single table? Thanks Jerry -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
[GENERAL] How can I merge two tables?
Hi, I have tables on my various computers that looks like: Table "public.registrations" Column | Type | Modifiers | Storage | Description --+--+---+--+- software | text | | extended | id | text | | extended | value| text | | extended | location | text | | extended | Indexes: "registrations_software_idx" btree (software) CLUSTER Has OIDs: yes I keep registration numbers for software and login/passwords for various organizations, etc… As time goes by the tables on the various computers get out of sync. Is there an elegant way I can get all of the differences (uniquely) merged into a single table? Thanks Jerry -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
[GENERAL] Installing Fedora 15 hosed my db...
> > > On Jun 16, 2011, at 5:16 PM, Dagan McGregor wrote: > >> On Thu, 16 Jun 2011 15:01:30 -0400, Jerry LeVan wrote: >>> Yesterday I upgraded from fedora 14 to fedora 15... >>> >>> The install process sorta trashed my 8.4 db...here is >>> what I have: >>> postgresql-server-9.0.4-1.fc15.i686 >>> postgresql-pltcl-8.4.4-1PGDG.fc12.i386 >>> postgresql-docs-8.4.4-1PGDG.fc12.i386 >>> postgresql-libs-9.0.4-1.fc15.i686 >>> postgresql-contrib-8.4.4-1PGDG.fc12.i386 >>> postgresql-9.0.4-1.fc15.i686 >>> postgresql-plpython-8.4.4-1PGDG.fc12.i386 >>> postgresql-devel-8.4.4-1PGDG.fc12.i386 >> >> [...] >>> Any suggestions on how I can cleanup the mess I created *and* get >>> a complete 9.0.4 installation? >> >> Just curious, why do you have Fedora 12 packages in the package list, if >> you're running Fedora 14? If you've been upgrading from Fedora 12, that >> would be part of the problem. Fedora doesn't update between older versions >> all that well. >> >> I'd suggest, if you do have a data back-up, it would be easier to do a clean >> install of Fedora 15. >> >> Dagan > As I noted earlier today, I had made postgresql 'invisible' to yum in the fedora repo... When I made it visible all of the missing f15 postgresql rpms showed up in yumex. When I installed the missing rpms the older fedora rpms vanished and I was able to do as Tom suggested: service postgresql pg_upgrade and the conversion was successful :) I am now running version Pg 9.0.4. Jerry -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
Re: [GENERAL] Installing Fedora 15 hosed my db...
On Thu, 2011-06-16 at 16:05 -0400, Tom Lane wrote: > Jerry LeVan writes: > > Yesterday I upgraded from fedora 14 to fedora 15... > > The install process sorta trashed my 8.4 db...here is > > what I have: > > postgresql-server-9.0.4-1.fc15.i686 > > postgresql-pltcl-8.4.4-1PGDG.fc12.i386 > > postgresql-docs-8.4.4-1PGDG.fc12.i386 > > postgresql-libs-9.0.4-1.fc15.i686 > > postgresql-contrib-8.4.4-1PGDG.fc12.i386 > > postgresql-9.0.4-1.fc15.i686 > > postgresql-plpython-8.4.4-1PGDG.fc12.i386 > > postgresql-devel-8.4.4-1PGDG.fc12.i386 > > > Any suggestions on how I can cleanup the mess I created *and* get > > a complete 9.0.4 installation? > > Well, you could > (1) remove all the PGDG RPMs, > (2) install the regular Fedora postgresql RPMs, > including postgresql-upgrade > (3) run "service postgresql upgrade" > > (I haven't actually tested postgresql-upgrade in the context of > upgrading from 8.4 PGDG RPMs instead of the regular Fedora ones, but > in theory it should work. As always, a filesystem backup of your > database is a good thing to have in case of disaster.) > regards, tom lane Oh snap! I had excluded postgresql from the fedora repo because I had been using pgdg repo. When I enabled postgresql in the repo all of the missing rpms magically appeared in the yumex update section :0 Jerry -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
[GENERAL] Installing Fedora 15 hosed my db...
Yesterday I upgraded from fedora 14 to fedora 15... The install process sorta trashed my 8.4 db...here is what I have: postgresql-server-9.0.4-1.fc15.i686 postgresql-pltcl-8.4.4-1PGDG.fc12.i386 postgresql-docs-8.4.4-1PGDG.fc12.i386 postgresql-libs-9.0.4-1.fc15.i686 postgresql-contrib-8.4.4-1PGDG.fc12.i386 postgresql-9.0.4-1.fc15.i686 postgresql-plpython-8.4.4-1PGDG.fc12.i386 postgresql-devel-8.4.4-1PGDG.fc12.i386 I have a couple of other machines that that contain the db so I could do a pg_dumpall to get something to stuff into my db at the appropriate time. I would like to upgrade to 9.0.4... I could not find the contrib module for 9.0.4 module in yumex. I really need the dbink tool to keep the dbs on my machines up to date. Any suggestions on how I can cleanup the mess I created *and* get a complete 9.0.4 installation? Thanks, Jerry -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
[GENERAL] Create Table Question...
The docs ( 9.0.2) for create table asserts that a data type representing a row
of
the table is automatically created.
Tain't clear to me what this means...
Here is a fragment of sql that I frequently use:
*
insert into checks (select *
from dblink('select * from checks where date >=''1/1/2011''')
as (date date,
amount numeric(9,2),
tranid text,
source text,
memo text,
status text,
category text
) );
**
The stuff after the 'as' is a description of the
rows of the table checks.
Could I shortened the above by using the automatically created row type of
the table checks?
Thanks
Jerry
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
Re: [GENERAL] iPad and Pg revisited...
Trapped in Steve Jobs Reality Distortion Field On Jan 25, 2011, at 8:21 AM, John DeSoi wrote: > > On Jan 24, 2011, at 3:25 PM, Jerry LeVan wrote: > >> I assume that if I were to jump to Pg 9.x.x that phpPgAdmim would die, yes? > > I have not tried it, but my guess is it will work. I don't recall seeing that > there were any major protocol changes for version 9, so I suspect whatever > libpq version is linked to PHP should work just fine with Postgres 9. > You are correct :) I upgraded three of my Mac systems to 9.0.2 from 8.4.4. All went smoothly except that one of my gui apps quit displaying selection results... It turns out that the status I was checking now returns 'SELECT ' instead of just 'SELECT'. It took more than a few minutes to find and fix the problem. Jerry > > > > John DeSoi, Ph.D. > > > > -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
[GENERAL] iPad and Pg revisited...
I have cleaned up my simple Perl cgi script for accessing Postgresql db's... Thanks to Tom Lane's (aka the Wizard) hints the 'describe ' function now works :) The url: http://homepage.mac.com/levanj/Perl I also found a mac php package that has postgresql support ( My mac php systems do *not* support Pg), g. The package is located at: http://taracque.hu/php5/ The installation is basically plug and play ( Just have to add a couple of clauses to the apache config file). The existing Apple php system is not touched. phpPgAdmin fires right up after the installation. It looks almost as nice as my cgi ( Ok that is a liebut i am prejudiced :) I assume that if I were to jump to Pg 9.x.x that phpPgAdmim would die, yes? Thanks Jerry -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
Re: [GENERAL] How can I find the schema that a table belongs to?
On Jan 19, 2011, at 3:12 PM, DM wrote: > one of the way to find out schema name is like below > > select * from pg_tables where tablename like '%xyz%'; > schemaname | tablename | tableowner | tablespace | hasindexes | hasrules | > hastriggers > +---++++--+- > (0 rows) > > ~Deepak > That does not work if the user entered a 'view' in the sql box. Also a table/view could be in several schemas... Jerry -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
[GENERAL] How can I find the schema that a table belongs to?
Hi, I am trying to tidy up my perl script that runs as a cgi and allows remote users (aka me) to interact with my Pg database. I primarily want to use this tool as a way for my iPad to browse my data base. It seems to be working quite well but one certainly does not want to 'select * from ginormous_table'. I am trying to build a 'describe' function. ie if the user types "describe tablename" in the sql box I want to display some interesting attributes for that table, mainly names and data types for each of the columns. I have done this in other programs but I forced the user to specify a schema qualified name ( and mimiced what psql -E did). So I guess the question is: Given a bare table name, how can I recover the schema qualified name with whatever the current search path happens to be? This task has to be done using simple sql from the perl dbi. Thanks, Jerry -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
[GENERAL] How can I find a schema that a table belong to?
Hi, I am trying to tidy up my perl script that runs as a cgi and allows remote users (aka me) to interact with my Pg database. I primarily want to use this tool as a way for my iPad to browse my data base. It seems to be working quite well but one certainly does not want to 'select * from ginormous_table'. I am trying to build a 'describe' function. ie if the user types "describe tablename" in the sql box I want to display some interesting attributes for that table, mainly names and data types for each of the columns. I have done this in other programs but I forced the user to specify a schema qualified name ( and mimiced what psql -E did). So I guess the question is: Given a bare table name, how can I recover the schema qualified name with whatever the current search path happens to be? This task has to be done using simple sql from the perl dbi. Thanks, Jerry -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
Re: [GENERAL] iPad and Postgresql...
On Jan 17, 2011, at 11:30 AM, Gary Chambers wrote: > Jerry, > >>> http://www.gnegg.ch/2009/08/snow-leopard-and-php/ >> It sorta looks like the above might blow away the existing php stuff... > > Have you considered using the MacPorts version? That's what I use for > development on my Macs and I've never had a problem replicating my > production environments whether in Solaris or Linux. > >> Pointers to the apps if you please :) > > Search for postgres or postgresql in the iTunes store. DataGlass PostgreSQL > is one of the apps. I recall seeing another one a couple weeks back, but I > can't remember the name of it at the moment. > > -- Gary Chambers Sigh, I am trying to simplify life... I tried the DataGlass Postgresql app ( even paid for the upgrade so I could see more than a screen full of records). Regrettably I don't think it is ready for prime time...The interface is a bit clunky. It seemed to hang with trying to display pg_proc ;( I know that if I had to build a parallel apache, php, perl, etc that madness would just be a matter of weeks away... I have one of the community pythons installed and have to remember that when I build an extension for the Apple Python that I have to rename the Python an Tcl frameworks for the community python so the linker will not grab them instead of the apple specific frameworks... Didn't some guy named Harry say "A man has to know his limitations"? Jerry -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
Re: [GENERAL] iPad and Postgresql...
On Jan 17, 2011, at 10:48 AM, John DeSoi wrote: > > On Jan 16, 2011, at 7:40 PM, Andrej wrote: > >>> Is there an idiot installable package for MacOsX Snow Leopard that will >>> provide a 'better' user experience for accessing Pg via the web, especially >>> when viewed on the iPad? >> >> It's not perl, but have you considered >> http://phppgadmin.sourceforge.net/ > > I second this suggestion, but it is not as easy to install on the Mac as it > should be. Snow Leopard has no PostgreSQL support in the standard PHP > install. You can set it up yourself with the help of this article: Yes I was disappointed when the php-info function showed there was no pg support... > > http://www.gnegg.ch/2009/08/snow-leopard-and-php/ > It sorta looks like the above might blow away the existing php stuff... > There also seems to be some nice looking native iPad/iPhone apps with the > ability to perform ad-hoc queries using PostgreSQL. Pointers to the apps if you please :) Right now the rempgsql.pl cgi is starting to look better to me for read access to my db... Maybe after a few days rest...I am still reeling from a firmware corruption problem in my airport extreme base station, udp ports 500 and 4500 started to refuse to pass data in from the wan side. This made it impossible to access the VPN server. It took a while to diagnose and fix the problem. > > > John DeSoi, Ph.D. Jerry -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
[GENERAL] iPad and Postgresql...
Hi, I have an iPad and a small network of macs and fedora/windoze machines at home. I am running pg 8.4.4 on all of the 'real' computers. I have been hoping that some developer would create an iPad app that would allow me to access my home database ( i am getting a bit long in the tooth and remembering passwords for discussion groups and similar stuff is getting hard to remember). I can securely access my home net via VPN (or ssh ). I do have a terminal app on the iPad that groks ssh ( or just use the VPN). But psql on the terminal apps is not pleasant to use, I get a lot of wrapping due to the screen size... I recalled that I had written a 'cgi' that would let me connect to a pg database, execute sql and display the results in a html table. The bad news is that after 11 or so years my perl foo has vanished. This afternoon I tried my hand at installing the necessary perl modules to be able to talk to pg. I am running the latest MacOSX and using the Apple installed perl. I had to force install DBD::Pg and was afraid it would die when invoked. Much to my surprise the cgi worked! I can access the db and execute single sql statements and select results are displayed in a table. I have a 'more' button in case there are more than 500 rows... The cgi has two meta-commands, 'table' and 'describe '. The 'table' command lists all of the tables in a db and the describe command attempts to list the column names and data types ( does not work for schema qualified table names). So what I have does give me access to my Pg db from anywhere on my iPad but now that I have a taste: Is there an idiot installable package for MacOsX Snow Leopard that will provide a 'better' user experience for accessing Pg via the web, especially when viewed on the iPad? I would be grateful if a Perl/Pg person would take a look at the rempgsql.pl script and make it mo'better. The script is located at http://homepage.mac.com/levanj/Perl/ Thanks, Jerry -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
[GENERAL] Pgadmin for Fedora 14?
Hi, Is there a Fedora 14 rpm for pgadmin that works out of the box for pg 8 and pg 9? Thanks, Jerry Trapped in Steve Jobs Reality Distortion Field -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
[GENERAL] Is it safe...( Upgrade questions)
I am trying to screw up the courage to update my systems ( 2 macs, 2 fedora ) from the last 8.4 postgresql updates to the latest 9.0.1 versions. I have a couple of concerns... 1) I have developed my own gui apps using tcl/tk and wxpython for accessing and maintaining my db's. I use psycopg and pgtcl interfaces to libpq. Do these packages work ok with version 9? 2) The fedora postgresql rpms at pgrpms.org seem to have introduced a new naming convention and a new directory layout. It is not clear to me what the impact is going to be with respect to psycopg and pgtcl. I am guessing that I will have to rebuilt these packages and will not be able to use the standard Fedora releases. I guess a third option is to wait for Fedora 14... Can anyone share their experiences with installing on Fedora 13 ( in particular the problem with the interfaces with libpq) ? Thanks Jerry -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
Re: [GENERAL] Libpq on iPad?
On Aug 1, 2010, at 8:00 PM, ABPNI wrote: > > > On 2 Aug 2010, at 00:44, Jerry LeVan wrote: > >> Has anyone looked at the feasibility of building libpq as a first step >> towards building >> An iPad app that can talk to postgresql dbs ? >> >> Thanks >> >> Jerry >> >> Trapped in Steve Jobs Reality Distortion Field >> -- >> Sent via pgsql-general mailing list (pgsql-general@postgresql.org) >> To make changes to your subscription: >> http://www.postgresql.org/mailpref/pgsql-general > > I would have thought that only backend apps would talk to pgsql? > > Maybe there is a case to allow an ipad app to talk directly to a pgsql > database? Admin work? Once upon a time in a galaxy far, far away, I wrote gui apps ( Cocoa/Python/Tk) that allowed me to interact with Postgresql databases ( Think stripped down PgAdmin). It would be nice to be able to do the same on my iPad...but I guess that Python and Tk are out as developmental tools. (I have a ssh app that I can use but it is a bit clumsy...) Jerry -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
[GENERAL] Libpq on iPad?
Has anyone looked at the feasibility of building libpq as a first step towards building An iPad app that can talk to postgresql dbs ? Thanks Jerry Trapped in Steve Jobs Reality Distortion Field -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
Re: [GENERAL] Fedora 13 killed dblink this week...
On Jul 17, 2010, at 1:21 PM, Tom Lane wrote: > Jerry LeVan writes: >> I wish whoever is in charge of the yum rpm depository would get >> cracking on building the Fedora 13 repo... > > Uhm ... what's wrong with the Fedora-supplied PG RPMs? > > regards, tom lane For a long time Fedora rpms lagged the rpms that Devrim made for the yum repository. That is apparently no longer the case so I may well switch back :) Jerry -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
Re: [GENERAL] Fedora 13 killed dblink this week...
On Sat, 2010-07-17 at 08:49 -0700, Joe Conway wrote: > On 07/17/2010 08:12 AM, Tom Lane wrote: > > I wrote: > > Oh, and Theory 3: see if restarting your postgresql server fixes it. > > If you didn't restart then the old openldap libraries are probably > > still in the server's address space. I'm not sure exactly how that > > might lead to this symptom, but it sure looks like your libldap and > > liblber are out of sync somehow. > > FWIW, I just tested on fedora 13 and sure enough, I started with the > same error, and fixed it with a postgres restart. > > Joe > > Wow, Tom strikes again... The server restart fixed the problem. I wish whoever is in charge of the yum rpm depository would get cracking on building the Fedora 13 repo... Jerry -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
[GENERAL] Fedora 13 killed dblink this week...
I think that something bad has happened to Fedora 13 this week.
This morning when I tried the following:
select dblink_connect('host=mbp user=levan dbname=levan password=xx')
I got the following error:
Error: could not load library "/usr/lib/pgsql/dblink.so":
/usr/lib/libldap_r-2.4.so.2: undefined symbol: ber_sockbuf_io_udp
The above worked ok last week...
I am running postgresql 8.4.4 from the rpms
[je...@bigbox ~]$ rpm -qa | grep postgres
postgresql-8.4.4-1PGDG.fc12.i386
postgresql-server-8.4.4-1PGDG.fc12.i386
postgresql-pltcl-8.4.4-1PGDG.fc12.i386
postgresql-docs-8.4.4-1PGDG.fc12.i386
postgresql-libs-8.4.4-1PGDG.fc12.i386
postgresql-contrib-8.4.4-1PGDG.fc12.i386
postgresql-plpython-8.4.4-1PGDG.fc12.i386
postgresql-devel-8.4.4-1PGDG.fc12.i386
Also:
[je...@bigbox ~]$ ldd /usr/lib/libldap_r-2.4.so.2
linux-gate.so.1 => (0x00852000)
liblber-2.4.so.2 => /usr/lib/liblber-2.4.so.2 (0x03c3)
libresolv.so.2 => /lib/libresolv.so.2 (0x009a8000)
libsasl2.so.2 => /usr/lib/libsasl2.so.2 (0x03aaa000)
libssl.so.10 => /usr/lib/libssl.so.10 (0x037fc000)
libcrypto.so.10 => /lib/libcrypto.so.10 (0x034da000)
libpthread.so.0 => /lib/libpthread.so.0 (0x0080f000)
libc.so.6 => /lib/libc.so.6 (0x00681000)
libdl.so.2 => /lib/libdl.so.2 (0x0082c000)
libcrypt.so.1 => /lib/libcrypt.so.1 (0x00597000)
libgssapi_krb5.so.2 => /lib/libgssapi_krb5.so.2 (0x037cc000)
libkrb5.so.3 => /lib/libkrb5.so.3 (0x036e4000)
libcom_err.so.2 => /lib/libcom_err.so.2 (0x00dfa000)
libk5crypto.so.3 => /lib/libk5crypto.so.3 (0x0379f000)
libz.so.1 => /lib/libz.so.1 (0x0086a000)
/lib/ld-linux.so.2 (0x0065f000)
libfreebl3.so => /lib/libfreebl3.so (0x005c9000)
libkrb5support.so.0 => /lib/libkrb5support.so.0 (0x00646000)
libkeyutils.so.1 => /lib/libkeyutils.so.1 (0x00637000)
libselinux.so.1 => /lib/libselinux.so.1 (0x00981000)
This happens on *both* of my Fedora 13 boxen...
Any suggestions
Jerry
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
[GENERAL] Fedora 13 and yum.pgsqlrpms.org
Will the repository be updated for Fedora 13 in the near future :) I had to disable the repo because yumex croaks when it cannot find the repository. Jerry -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
Re: [GENERAL] Subscription Mess...
Begin forwarded message: > From: Jerry LeVan > Date: May 11, 2010 9:52:21 AM EDT > To: "pgsql-general@postgresql.org general" > Subject: Subscription Mess... > > Please excuse the intrusion... > > Last week, my subscription to pgsql-general quit coming to my mailbox... > > I logged into my account at postgresql.org and it showed that I was > stilled subscribed. > > In desperation I changed my email address ( to my gmail account) and the > subscription started > arriving again. > > While this was happening I switched over to imap for my home network > > When I try to read the digests on my Fedora boxen, the actual message > content is missing from many of the messages (but all of the headers are > present). > > I thought that perhaps Evolution ( the mail client in Fedora 12) might > be having problems parsing the digest so I tried logging back into > my postgresql account to see if there is a plain text option for the digest. > > Unfortunately the postgresql mail system will not let me login. It claims > that the credentials are not valid. > > When I ask the mail system to send instructions on changing the password > to my address, it says it sent mail but nothing ever arrives ( I even > tried my old address but again nothing ever arrives...)... > > I just got another digest while composing this message... > > I *can* read the digest on my mac and I can use a browser to see the > digest at gmail.com. > > How can I get control of my account again? > > Are there any options that perhaps would work so evolution can properly > display the digests? > > Thanks, > > Jerry > Ok, I think I was trying to do a "Community Login" when in fact I wanted to login to Majordomo. I think trying to get to the Majordomo login page is obscure at best... Anyway there appear to be 3 options for digests, indexed, mime, and plain text. Mime does not appear to work for Evolution in Fedora 12. I have reset to indexed format to see if that works better ( and still works on the mac). Sorry for the noise. Jerry -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
[GENERAL] Subscription Mess...
Please excuse the intrusion... Last week, my subscription to pgsql-general quit coming to my mailbox... I logged into my account at postgresql.org and it showed that I was stilled subscribed. In desperation I changed my email address ( to my gmail account) and the subscription started arriving again. While this was happening I switched over to imap for my home network When I try to read the digests on my Fedora boxen, the actual message content is missing from many of the messages (but all of the headers are present). I thought that perhaps Evolution ( the mail client in Fedora 12) might be having problems parsing the digest so I tried logging back into my postgresql account to see if there is a plain text option for the digest. Unfortunately the postgresql mail system will not let me login. It claims that the credentials are not valid. When I ask the mail system to send instructions on changing the password to my address, it says it sent mail but nothing ever arrives ( I even tried my old address but again nothing ever arrives...)... I just got another digest while composing this message... I *can* read the digest on my mac and I can use a browser to see the digest at gmail.com. How can I get control of my account again? Are there any options that perhaps would work so evolution can properly display the digests? Thanks, Jerry -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
Re: [GENERAL] Log File Melancholy
On Sep 23, 2009, at 7:46 PM, Tom Lane wrote: Jerry LeVan writes: could not lookup DNS configuration info service: (ipc/send) invalid destination port LOG: could not resolve "localhost": nodename nor servname provided, or not known LOG: disabling statistics collector for lack of working socket I cannot figure out where the "could not lookup DNS..." line is coming from... Presumably from inside getaddrinfo(), since the subsequent LOG message is Postgres complaining that getaddrinfo didn't work. Am I unique? Works for me on both 32- and 64-bit Snow Leopard installations, and for at least one Snow Leopard machine in the buildfarm. There must be something funny about the DNS configuration on your machines, but there's no way to tell what from here. regards, tom lane Snow Leopard and Postgresql works for me *finally*. I did a clean install on a spare firewire disk and only added the postgresql stuff. I did a 64bit build, inited the db and imported a dump from the other system. I started the database manually as in the INSTALL note and everything started properly. I just about decided that I needed to do a clean install on my main machine, but I decided to do one more test. I copied the PostgreSQL StartupItem directory from my main machine and rebooted. I got the same errors as I have been complaining about! A few more tweaks and restarts showed I could manually restart postgresql from the command line but I could not start postgresql properly from the StartupItems boot process. I have been using the same startup setup for years and years I suspected that the problem was that the Postgresql system was getting started too early. I installed the osx startup items in the contrib directory and tweeked the startup script to point to the nonstandard place I have the binaries. I now get a clean startup ( Stats collector on and Autovacuum on) and as an extra bonus dblink_connect is again resolving names :) Whew! Jerry -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
[GENERAL] Log File Melancholy
Hi,
I have two Snow Leopard installations, a macbook pro and a mac mini.
Whenever I start the postgresql system on the mbp the log shows:
LOG: received smart shutdown request
LOG: shutting down
LOG: database system is shut down
could not lookup DNS configuration info service: (ipc/send) invalid
destination port
LOG: could not resolve "localhost": nodename nor servname provided,
or not known
LOG: disabling statistics collector for lack of working socket
WARNING: autovacuum not started because of misconfiguration
HINT: Enable the "track_counts" option.
LOG: database system was shut down at 2009-09-21 11:24:17 EDT
LOG: database system is ready to accept connections
on the Mac Mini I get:
LOG: database system is shut down
could not lookup DNS configuration info service: (ipc/send) invalid
destination port
LOG: could not resolve "localhost": nodename nor servname provided,
or not known
LOG: disabling statistics collector for lack of working socket
WARNING: autovacuum not started because of misconfiguration
HINT: Enable the "track_counts" option.
DNSServiceDiscoveryLookupServer(): {/SourceCache/mDNSResponder/
mDNSResponder-212.1/mDNSMacOSX/DNSServiceDiscovery.c:143}
bootstrap_look_up() failed: $1003
LOG: database system was shut down at 2009-09-11 14:21:01 EDT
LOG: database system is ready to accept connections
Both are 32 bit builds...
I cannot figure out where the "could not lookup DNS..." line
is coming from...
Am I unique?
Jerry
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
Re: [GENERAL] How can I make a two arch libpq for snow leopard?
On Sep 20, 2009, at 7:47 PM, Scott Ribe wrote: The only thing that comes to mind is two separate build trees, one 32bit and the other 64bit and then somehow gluing the two libpqs together... Basically, probably the easiest way to proceed--man lipo to figure out how to combine the libraries. Yes, I found the lipo command this morning after reading the man page for the arch command :) I glued together the x86_64 and i386 libpq5.2.dylibs and copied it into the pgsql library directory and restarted the server...looks like it is working ok... With the fat libpq I was able build both of the database interfaces pgtcl and psycopg2. By default the interface libs where created as fat libraries so I can build/run pg apps using Apple tcl 32/64 bit or Apple python 32/64 bit. ( the arch command can force Apple tcl to run in 32 bit mode). My remaining problems are: 1) dblink_connect cannot resolve names, I have to use IP's. 2) My once rock solid WxPython based Postgresql browser has gone sideways. After a couple of selects the app vanishes in a puff of smoke or it hangs. Jerry -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
[GENERAL] How can I make a two arch libpq for snow leopard?
Hi, I have a i386 version of postgresql 8.4.1 created by setting export CC="gcc -arch i386" an then doing the config, make and make install. In particular libpq is an i386 library. Now I use two database 'adaptors' psycopg2 for python and pgtcl-ng for tcl. The python I use is from python.org (2.6.2). It is a 32 bit system. I can compile psycopg2 with the above python and it seems to be working ok. If I compile psycopg2 against the Apple python (2.6.1) I need to tell Python to run in thirty two bit mode else there will be libpq link problems. In order to use psycopg2 with the Apple python I then have to tell python to run in 32 bit mode using VERSIONER_PYTHON_PREFER_32_BIT=yes On the other hand... The does not appear to be a nifty switch to tell Apple's Tcl to run in 32 bit mode. Inorder to compile pgtcl-ng (aka pgtcl 1.7.0 ) I have to do a 32 bit compile by setting export CC="gcc -arch i386" then doing a configure, make and install. A standard compile trys to build a 64 bit object but fails because libpq is only a 32 bit library. The i386 compile "works" but tcl cannot load the resulting shared library with bad architecture error ( I guess it wants 64 bit). Now I also have an ActiveState 32 bit version of tcl and compiling pgtcl-ng against the active state tcl gives a loadable extension. So the question is: How can I build a libpq.dylib that can be loaded by either 32bit or 64bit applications? The only thing that comes to mind is two separate build trees, one 32bit and the other 64bit and then somehow gluing the two libpqs together... If the above is possible what happens when a 64 bit app tries to talk to the 32 bit server? If the previous question is true and I have the 64 bit libpq library loaded and then a 32 bit app talks to the server will the 32 bit libpq library then also be loaded in memory? I guess I also need to try and build a dual architecture for dblink... Am I confused? Thanks for any input :) Jerry -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
Re: [GENERAL] More Snow Leopard problems...
On Sep 7, 2009, at 9:37 AM, Jan Otto wrote:
hi jerry,
could not lookup DNS configuration info service: (ipc/send) invalid
destination port
LOG: could not resolve "localhost": nodename nor servname provided,
or not known
LOG: disabling statistics collector for lack of working socket
WARNING: autovacuum not started because of misconfiguration
HINT: Enable the "track_counts" option.
DNSServiceDiscoveryLookupServer(): {/SourceCache/mDNSResponder/
mDNSResponder-212.1/mDNSMacOSX/DNSServiceDiscovery.c:143}
bootstrap_look_up() failed: $1003
I wonder whether adding or removing --with-bonjour (whichever way
you didn't configure it) would make a difference.
try killing mDNSResponder before restarting postgres:
sudo killall mDNSResponder
hopefully apple fixes this dns-problems in 10.6.1.
regards, jan otto
The rascal gets respawned immediately ;(
Jerry
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
Re: [GENERAL] More Snow Leopard problems...
On Sep 7, 2009, at 11:36 AM, Adrian Klaver wrote:
On Monday 07 September 2009 6:03:28 am Jerry LeVan wrote:
On Sep 6, 2009, at 7:29 PM, Tom Lane wrote:
Jerry LeVan writes:
I have compiled a 32 bit ( CC="gcc -arch i386" ) version of
PG 8.4.0.
Since that's not the default on SL, have you tried 64 bit?
could not lookup DNS configuration info service: (ipc/send) invalid
destination port
LOG: could not resolve "localhost": nodename nor servname
provided,
or not known
LOG: disabling statistics collector for lack of working socket
WARNING: autovacuum not started because of misconfiguration
HINT: Enable the "track_counts" option.
DNSServiceDiscoveryLookupServer(): {/SourceCache/mDNSResponder/
mDNSResponder-212.1/mDNSMacOSX/DNSServiceDiscovery.c:143}
bootstrap_look_up() failed: $1003
I wonder whether adding or removing --with-bonjour (whichever way
you didn't configure it) would make a difference.
regards, tom lane
I have killed my database
I rebuilt Postgresql 8.4.0 as a 64 bit system without bonjour...no
errors
I stopped the backend via pg_ctl stop -D /usr/local/pgsql/data
I installed the freshly compiled code
I restarted the postgresql backend with /sbin/SystemStarted start
PostgreSQK
The system does not start because of a checksum error in a control
file...
Here is the end of the logfile:
LOG: received smart shutdown request <--- the shutdown command
LOG: shutting down
LOG: database system is shut down
FATAL: incorrect checksum in control file <--- when I try to
restart.
FATAL: incorrect checksum in control file <--- second try at
restarting...
Is there any way I can recover?
Jerry
I do not see an initdb in your sequence. You are probably seeing a
problem with
the 64 bit version of Postgres trying to read a 32 bit cluster.
--
Adrian Klaver
akla...@comcast.net
GackIs that documented anywhere?
Anyway due to advanced bit rot (machine refusing to boot) I had to
restore the whole
machine from from Friday's backup and add the missing records from my
10 year old db...
Snow Leopard needs a bit of work... On my main machine, a macbook
pro3,1 the mds processes
keep dumping core and so spotlight does not work ( and for some reason
I have to reboot
my Airport Extreme Base Station when when the repeated core dumps
start heating the machine).
I have not had any problems on my generic local server a core duo mac
mini (which I think is
a 32 bit machine).
It is still not clear to me why dblink cannot do name resolution on my
64 bit machine...
In any case I am back on the air and postgresql seems to be working
mod the dblink problem.
Thanks,
Jerry
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
Re: [GENERAL] More Snow Leopard problems...
On Sep 6, 2009, at 7:29 PM, Tom Lane wrote:
Jerry LeVan writes:
I have compiled a 32 bit ( CC="gcc -arch i386" ) version of
PG 8.4.0.
Since that's not the default on SL, have you tried 64 bit?
could not lookup DNS configuration info service: (ipc/send) invalid
destination port
LOG: could not resolve "localhost": nodename nor servname provided,
or not known
LOG: disabling statistics collector for lack of working socket
WARNING: autovacuum not started because of misconfiguration
HINT: Enable the "track_counts" option.
DNSServiceDiscoveryLookupServer(): {/SourceCache/mDNSResponder/
mDNSResponder-212.1/mDNSMacOSX/DNSServiceDiscovery.c:143}
bootstrap_look_up() failed: $1003
I wonder whether adding or removing --with-bonjour (whichever way
you didn't configure it) would make a difference.
regards, tom lane
I have killed my database
I rebuilt Postgresql 8.4.0 as a 64 bit system without bonjour...no
errors
I stopped the backend via pg_ctl stop -D /usr/local/pgsql/data
I installed the freshly compiled code
I restarted the postgresql backend with /sbin/SystemStarted start
PostgreSQK
The system does not start because of a checksum error in a control
file...
Here is the end of the logfile:
LOG: received smart shutdown request <--- the shutdown command
LOG: shutting down
LOG: database system is shut down
FATAL: incorrect checksum in control file <--- when I try to restart.
FATAL: incorrect checksum in control file <--- second try at
restarting...
Is there any way I can recover?
Jerry
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
[GENERAL] More Snow Leopard problems...
I have compiled a 32 bit ( CC="gcc -arch i386" ) version of
PG 8.4.0.
I am finding the following in the pg logfile when I stop then start
the postgresql server.
LOG: received smart shutdown request
LOG: shutting down
LOG: database system is shut down
could not lookup DNS configuration info service: (ipc/send) invalid
destination port
LOG: could not resolve "localhost": nodename nor servname provided,
or not known
LOG: disabling statistics collector for lack of working socket
WARNING: autovacuum not started because of misconfiguration
HINT: Enable the "track_counts" option.
DNSServiceDiscoveryLookupServer(): {/SourceCache/mDNSResponder/
mDNSResponder-212.1/mDNSMacOSX/DNSServiceDiscovery.c:143}
bootstrap_look_up() failed: $1003
LOG: database system was shut down at 2009-09-06 10:05:29 EDT
LOG: database system is ready to accept connections
There is some wonkiness going on...dblink cannot resolve computers by
name,
I have to specify the actual IP address.
I am running a local dns server for my local network (skynet) and all
of the other
networking aware software I have tried appears to be working ok.
Netstat shows postgresql is listening on port 5432 (tcp) and /
tmp/.s.PGSQL.5432 (Unix Domain)
Here is what nslookup says about "localhost"
bash-3.2# nslookup localhost
Server: 192.168.1.90
Address:192.168.1.90#53
Name: localhost.skynet
Address: 127.0.0.1
Anyone else have similar problems on Snow Leopard?
Any suggestions?
Thanks
Jerry
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
Re: [GENERAL] Snow Leopard and plpython problem
On Sep 3, 2009, at 11:01 AM, Jan Otto wrote: hi jerry, Hi I am having a problem building Postgresql 8.4.0 in Snow Leopard. I cannot get plpython to build... I have installed MacPython 2.6.2 in /Library/Frameworks/ Python.framework do you really need python 2.6.2? snow leopard has python 2.6.1 on board and there are no problems compiling/using postgresql with the python that comes with snow leopard. The binary: mbp:postgresql-8.4.0 postgres$ which python /Library/Frameworks/Python.framework/Versions/Current/bin/python mbp:postgresql-8.4.0 postgres$ file `which python` /Library/Frameworks/Python.framework/Versions/Current/bin/python: Mach-O universal binary with 2 architectures /Library/Frameworks/Python.framework/Versions/Current/bin/python (for architecture ppc): Mach-O executable ppc /Library/Frameworks/Python.framework/Versions/Current/bin/python (for architecture i386):Mach-O executable i386 you need the 64-bit version of python (x86_64) or try compile postgresql 32-bit (i386) asche:~ asche$ file `which python` /usr/bin/python: Mach-O universal binary with 3 architectures /usr/bin/python (for architecture x86_64): Mach-O 64-bit executable x86_64 /usr/bin/python (for architecture i386):Mach-O executable i386 /usr/bin/python (for architecture ppc7400): Mach-O executable ppc ./configure --bindir=/usr/local/bin --mandir=/usr/local/share/man \ --enable-thread-safety \ --with-python \ --with-perl --with-tcl \ --with-libedit-preferred \ --with-openssl --with-bonjour Configure completes ok. When I do a "make 2>mylog.log" i have tried configuring an building with the same options as you and it compiles without an error or warning about python. regards, jan otto Jan, Thanks for convincing me that it could be done... It appears to me that even though I simplified my PATH to a bare minimum that the link process was picking up the framework in /Library/Frameworks/ Python instead of /System/Library/Frameworks/Python.framework. I renamed /Library/Frameworks/Python so it was no longer visible and the build succeeded. Jerry -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
[GENERAL] Snow Leopard and plpython problem
Hi I am having a problem building Postgresql 8.4.0 in Snow Leopard. I cannot get plpython to build... I have installed MacPython 2.6.2 in /Library/Frameworks/Python.framework The binary: mbp:postgresql-8.4.0 postgres$ which python /Library/Frameworks/Python.framework/Versions/Current/bin/python mbp:postgresql-8.4.0 postgres$ file `which python` /Library/Frameworks/Python.framework/Versions/Current/bin/python: Mach- O universal binary with 2 architectures /Library/Frameworks/Python.framework/Versions/Current/bin/python (for architecture ppc): Mach-O executable ppc /Library/Frameworks/Python.framework/Versions/Current/bin/python (for architecture i386): Mach-O executable i386 mbp:postgresql-8.4.0 postgres$ echo $PATH /Library/Frameworks/Python.framework/Versions/Current/bin:/usr/bin:/ bin:/usr/sbin:/sbin:/usr/local/bin:/usr/X11/bin mbp:postgresql-8.4.0 postgres$ python Python 2.6.2 (r262:71600, Apr 16 2009, 09:17:39) [GCC 4.0.1 (Apple Computer, Inc. build 5250)] on darwin Type "help", "copyright", "credits" or "license" for more information I use the following config params: mbp:postgresql-8.4.0 postgres$ cat configJHL ./configure --bindir=/usr/local/bin --mandir=/usr/local/share/man \ --enable-thread-safety \ --with-python \ --with-perl --with-tcl \ --with-libedit-preferred \ --with-openssl --with-bonjour Configure completes ok. When I do a "make 2>mylog.log" The build fails on gcc -no-cpp-precomp -O2 -Wall -Wmissing-prototypes -Wpointer-arith - Wdeclaration-after-statement -Wendif-labels -fno-strict-aliasing -fwrapv -bundle -multiply_defined suppress plpython.o -bundle_loader ../../../src/backend/postgres -L../../../src/port - framework Python -o plpython.so The contents of mylog.log are: postmaster.c: In function ‘PostmasterMain’: postmaster.c:859: warning: ‘DNSServiceRegistrationCreate’ is deprecated (declared at /usr/include/DNSServiceDiscovery/ DNSServiceDiscovery.h:139) pgc.c:4363: warning: ‘yy_flex_realloc’ defined but not used ld: warning: in ../../../src/backend/postgres, file is not of required architecture ld: warning: in plperl.o, file is not of required architecture ld: warning: in spi_internal.o, file is not of required architecture ld: warning: in SPI.o, file is not of required architecture ld: warning: in ../../../src/backend/postgres, file is not of required architecture ld: warning: in plperl.o, file is not of required architecture ld: warning: in spi_internal.o, file is not of required architecture ld: warning: in SPI.o, file is not of required architecture ld: warning: in /Library/Frameworks//Python.framework/Python, missing required architecture x86_64 in file Undefined symbols: "_PyDict_DelItemString", referenced from: _PLy_function_delete_args in plpython.o "_PyIter_Next", referenced from: _PLy_function_handler in plpython.o "_PyFloat_FromDouble", referenced from: _PLyFloat_FromString in plpython.o "_PyErr_Fetch", referenced from: _PLy_elog in plpython.o "_PyErr_NewException", referenced from: __PG_init in plpython.o __PG_init in plpython.o __PG_init in plpython.o "_PyErr_GivenExceptionMatches", referenced from: _PLy_elog in plpython.o _PLy_elog in plpython.o "_PyDict_GetItemString", referenced from: _PLy_modify_tuple in plpython.o _PLy_procedure_get in plpython.o "_Py_Initialize", referenced from: __PG_init in plpython.o "_PyArg_ParseTuple", referenced from: _PLy_plan_status in plpython.o _PLy_spi_prepare in plpython.o _PLy_spi_execute in plpython.o _PLy_spi_execute in plpython.o "_PyList_New", referenced from: _PLy_trigger_build_args in plpython.o _PLy_function_build_args in plpython.o _PLy_spi_execute_fetch_result in plpython.o _PLy_spi_execute_fetch_result in plpython.o "_PyCObject_FromVoidPtr", referenced from: _PLy_procedure_create in plpython.o "_PyRun_StringFlags", referenced from: _PLy_procedure_create in plpython.o "_PyDict_GetItem", referenced from: _PLy_modify_tuple in plpython.o "_PyObject_GetIter", referenced from: _PLy_function_handler in plpython.o "_PySequence_Check", referenced from: _PLy_function_handler in plpython.o _PLy_spi_prepare in plpython.o _PLy_spi_execute_plan in plpython.o "_PyMapping_GetItemString", referenced from: _PLyMapping_ToTuple in plpython.o "_PySequence_Size", referenced from: _PLySequence_ToTuple in plpython.o _PLy_spi_prepare in plpython.o _PLy_spi_execute_plan in plpython.o "_PyErr_NormalizeException", referenced from: _PLy_elog in plpython.o "_PySequence_GetItem", referenced from: _PLySequence_ToTuple in plpython.o _PLy_spi_prepare in plpython.o _PLy_spi_execute_plan in plpython.o "_PyObject_GetAttrString", referenced from: _PLyObject_ToTuple in plpython.o "_PyBool_FromLong", referenced from: _PLyBool_FromString in plpython.o _
Re: [GENERAL] Snow Leopard and PG 8.4 problems....
On Aug 29, 2009, at 2:40 PM, Martin Gainty wrote:
for superusers only
dblink-connect takes a libpq style connection string with hostaddr
as first attribute
dblink("hostaddr=127.0.0.1 port=5432 dbname=mydb user=postgres
password=mypasswd");
http://www.postgresql.org/docs/current/static/contrib-dblink-connect.html
Martin Gainty
I have been able to use just the ip in the host field but Snow Leopard
seems to have
broken using a 'name' in the host field... see below.
It appears that compiling pg 8.4 gives rise to libs with architecture
of x386_64...
What sort of magic do I have to use to get a 32 bit version of the
various libs ?
( I don't seem to be able to find where in the make file I can ask the
linker to
add the various archs, but I am getting bleary eyed.)
I don't seem to be able to compile python support against the apple
2.6 or the macpython
2.5 versions (of python).
Has anyone built a Snow Leopard version of pg with python support?
Am I the only one to have problems with dblink on Snow Leopard?
( the fedora 11 rpms work fine...)
Jerry
> From: jerry.le...@eku.edu
> Subject: [GENERAL] Snow Leopard and PG 8.4 problems
> Date: Sat, 29 Aug 2009 12:08:45 -0400
> To: pgsql-general@postgresql.org
>
> Gh,
>
> Last week postgresql was working fine, yesterday I upgraded to
> Snow Leopard...
>
> Everything seemed to be working and then I tried to move some
> rows to another machine via dblink.
>
> I am getting a variety of failures on dblink_connect..
>
> mbp is my main machine let me connect to my home server ( named
server )
>
> [mbp:~]$ psql -Ulevan -hserver
> psql (8.4.0)
> Type "help" for help.
>
> levan=# select dblink_connect('host=mbp.skynet user=levan
dbname=levan
> password=foobar');
> ERROR: could not establish connection
> DETAIL: could not translate host name "mbp.skynet" to address:
> nodename nor servname provided, or not known
>
> levan=# select dblink_connect('host=mbp user=levan dbname=levan
> password=foobar');
> ERROR: could not establish connection
> DETAIL: could not translate host name "mbp" to address: nodename nor
> servname provided, or not known
>
> levan=# select dblink_connect('host=mbp.localdomain user=levan
> dbname=levan password=foobar');
> ERROR: could not establish connection
> DETAIL: could not translate host name "mbp.localdomain" to address:
> nodename nor servname provided, or not known
>
> levan=# select dblink_connect('host=192.168.1.80 user=levan
> dbname=levan password=foobar');
> dblink_connect
>
> OK
> (1 row)
>
> The name resolution appears to be buggered. Now server is almost my
> local network name
> server and it appears to be working just fine ie I can use Safari
send
> mail etc...
>
> Now if I hop on to server and connect to mbp psql and try to use
> dblink...
>
> [mbp:~]$ ssh server
> Password:
> Last login: Sat Aug 29 11:10:48 2009 from mbp.localdomain
> server:~ jerry$ psql -Ulevan -hmbp
> psql (8.4.0)
> Type "help" for help.
>
> levan=# select dblink('host=server user=levan dbname=levan
> password=foobar');
> ERROR: function dblink(unknown) does not exist
> LINE 1: select dblink('host=server user=levan dbname=levan
password=...
> ^
> HINT: No function matches the given name and argument types. You
> might need to add explicit type casts.
>
> ***
> Everything was working fine till the installation of Snow Leopard.
>
> I tried to rebuild dblink but got many bizarre errors.
>
> I tried to rebuild postgresql 8.4 but there were problems with
python
> and warnings about perl
> the build did not succeed.
>
> Anyone else having problems?
>
> Jerry
>
>
> --
> Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-general
With Windows Live, you can organize, edit, and share your photos.
Click here.
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
[GENERAL] Snow Leopard and PG 8.4 problems....
Gh,
Last week postgresql was working fine, yesterday I upgraded to
Snow Leopard...
Everything seemed to be working and then I tried to move some
rows to another machine via dblink.
I am getting a variety of failures on dblink_connect..
mbp is my main machine let me connect to my home server ( named server )
[mbp:~]$ psql -Ulevan -hserver
psql (8.4.0)
Type "help" for help.
levan=# select dblink_connect('host=mbp.skynet user=levan dbname=levan
password=foobar');
ERROR: could not establish connection
DETAIL: could not translate host name "mbp.skynet" to address:
nodename nor servname provided, or not known
levan=# select dblink_connect('host=mbp user=levan dbname=levan
password=foobar');
ERROR: could not establish connection
DETAIL: could not translate host name "mbp" to address: nodename nor
servname provided, or not known
levan=# select dblink_connect('host=mbp.localdomain user=levan
dbname=levan password=foobar');
ERROR: could not establish connection
DETAIL: could not translate host name "mbp.localdomain" to address:
nodename nor servname provided, or not known
levan=# select dblink_connect('host=192.168.1.80 user=levan
dbname=levan password=foobar');
dblink_connect
OK
(1 row)
The name resolution appears to be buggered. Now server is almost my
local network name
server and it appears to be working just fine ie I can use Safari send
mail etc...
Now if I hop on to server and connect to mbp psql and try to use
dblink...
[mbp:~]$ ssh server
Password:
Last login: Sat Aug 29 11:10:48 2009 from mbp.localdomain
server:~ jerry$ psql -Ulevan -hmbp
psql (8.4.0)
Type "help" for help.
levan=# select dblink('host=server user=levan dbname=levan
password=foobar');
ERROR: function dblink(unknown) does not exist
LINE 1: select dblink('host=server user=levan dbname=levan password=...
^
HINT: No function matches the given name and argument types. You
might need to add explicit type casts.
***
Everything was working fine till the installation of Snow Leopard.
I tried to rebuild dblink but got many bizarre errors.
I tried to rebuild postgresql 8.4 but there were problems with python
and warnings about perl
the build did not succeed.
Anyone else having problems?
Jerry
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
Re: [GENERAL] Messed up dblink...
On Mar 21, 2009, at 12:37 PM, Tom Lane wrote:
Jerry LeVan writes:
Something seems to have messed up my dblink interface...
The only thing I can think that has changed the last week
was the installation of 8.3.7.
What version were you using beforehand? Are you *sure* nothing else
in
your environment has changed?
levan=# select dblink_connect('host=mbp user=levan dbname=levan
password=foobar')
levan-# ;
ERROR: could not establish connection
DETAIL: could not translate host name "mbp" to address: Temporary
failure in name resolution
... because it is really, really hard to see how that particular
failure could arise from anything except a broken DNS configuration.
Try "nslookup mbp" at the shell command prompt. If that fails with
a similar error message, Postgres is not at fault.
regards, tom lane
Ok,
I found that for all of my boxen that if I connected to 'server' that
I could not connect back via dblink to the original host!
The nslookup worked fine in every case...
'server' is also my local nameserver. I took a flier and rebooted
the rascal and everything started working again :)
Thanks for the hint.
Jerry
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
[GENERAL] Messed up dblink...
Something seems to have messed up my dblink interface...
The only thing I can think that has changed the last week
was the installation of 8.3.7.
It has been a long time since I have had to think about
the installation of the dblink package...
The basic situation is as follows...
I have my main financial db on my Mac Book Pro 'mbp' and
backed up to my home server 'server' a Mac Mini and
also a linux box 'linuxbox'.
All currently running pg 8.3.7
I load my financial info weekly into the mac book pro
and then transfer the new data to the 'server' and
'linuxbox'.
I do this by connecting say to 'server' and then
connecting back to 'mbp' via dbilink and then pulling
the new data back to 'server' via dblink calls.
Here is a simplified version of the problem...
[mbp:~]$ psql -hserver -Ulevan
Welcome to psql 8.3.7, the PostgreSQL interactive terminal.
Type: \copyright for distribution terms
\h for help with SQL commands
\? for help with psql commands
\g or terminate with semicolon to execute query
\q to quit
levan=# select dblink_connect('host=mbp user=levan dbname=levan
password=foobar')
levan-# ;
ERROR: could not establish connection
DETAIL: could not translate host name "mbp" to address: Temporary
failure in name resolution
levan=# \q
The above error did not occur last week prior to the installation of
8.3.7
Going the other way...
server:~ jerry$ psql -hmbp -Ulevan
Welcome to psql 8.3.7, the PostgreSQL interactive terminal.
Type: \copyright for distribution terms
\h for help with SQL commands
\? for help with psql commands
\g or terminate with semicolon to execute query
\q to quit
levan=# select dblink_connect('host=server user=levan dbname=levan
password=foobar')
levan-# ;
dblink_connect
OK
(1 row)
Seems to work.
Also connecting to the linuxbox and coming back seems to work...
[mbp:~]$ psql -hlinuxbox -Ulevan
Welcome to psql 8.3.7, the PostgreSQL interactive terminal.
Type: \copyright for distribution terms
\h for help with SQL commands
\? for help with psql commands
\g or terminate with semicolon to execute query
\q to quit
levan=# select dblink_connect('host=mbp user=levan dbname=levan
password=foobar');
dblink_connect
OK
(1 row)
levan=# \q
I did a make and make install in the dblink directory on both
server and mbp and the results did not change...
any suggestions?
Thanks
Jerry
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
Re: [GENERAL] OS X library path issues for libpq (ver 8.3
Have you tried putting your environmental variables in: .MacOSX I have some apps that need access to some PG enviromental variables and I had to put them in a plist in the directory .MacOSX e.g. [mbp:~/.MacOSX]$ ls -al ~/.MacOSX total 8 drwxr-xr-x3 jerry jerry 102 Jun 25 2007 . drwxr-xr-x+ 113 jerry jerry 3842 Sep 7 12:45 .. -rw-r--r--1 jerry jerry 334 Jun 25 2007 environment.plist and [mbp:~/.MacOSX]$ cat environment.plist http://www.apple.com/DTDs/PropertyList-1.0.dtd "> PGDATABASE levan PGHOST localhost PGUSER levan The plist contents act like regular unix style environmental variables for apps started from the Finder. Perhaps placing the path informationfor the dynamic loader in the plist would solve your problems. Jerry -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
Re: [GENERAL] Universal libpq.a ?
On Feb 4, 2008, at 1:25 PM, Tom Lane wrote: "Dave Page" <[EMAIL PROTECTED]> writes: The Mac build of EDB Postgres is universal throughout, Yeah? How painful is it? We've had more than one request to enable universal builds. regards, tom lane Here is a config file I tried mbp:postgresql-8.3.0 postgres$ more configJHLFat ./configure --bindir=/usr/local/bin --mandir=/usr/local/share/man \ --enable-thread-safety \ --enable-multibyte --with-perl --with-tcl \ --with-python --with-libedit-preferred \ --with-openssl --with-bonjour \ CFLAGS='-isysroot /Developer/SDKs/MacOSX10.4u.sdk -arch i386 -arch ppc' \ LDFLAGS='-Wl,-syslibroot,/Developer/SDKs/MacOSX10.4u.sdk -arch ppc - arch i386' \ LDFLAGS_SL='-Wl,-syslibroot,/Developer/SDKs/MacOSX10.4u.sdk -arch ppc -arch i386' \ MACOSX_DEPLOYMENT_TARGET=10.4 I tried for a while to build the rascal and found the sticky point was invoking "ld". The man page for ld asserts that ld will only output a "thin" object file. In particular all of the SUBSYS.o files would default to plain old mach-o files. Eventually this caused problems during later linking. The man page for ld tantalized me by stating that gcc would automagically be enabled to build fat objects an invoke lipo to build a fat object. All of the *.o files generated by gcc where in fact fat object files. In fact I went to the interfaces directory and into the libpq subdirectory and invoked make and was able to build a "fat" libpq.a I was able to build an intel binary without any problems but it will be a couple of days before I find out if the "fat" libpq.a is actually functional ;( Jerry ---(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
[GENERAL] Universal libpq.a ?
Hi, I am trying to bring one of my Cocoa based Postgresql browsers up to date. I would like to create a "universal", ie works on PPC and Intel Macintosh platforms, version of the application. I guess the initial task would be to build a universal version of libpq.a. In the past I have created simple universal (command line) apps by adding CFLAGS=-isysroot /Developer/SDKs/MacOSX10.4u.sdk -arch i386 -arch ppc LDFLAGS=-Wl,-syslibroot,/Developer/SDKs/MacOSX10.4u.sdk -arch ppc - arch i386 to the make file and adding an environmental variable MACOSX_DEPLOYMENT_TARGET=10.4 Has anyone built a universal libpq.a? Which make files should I target for modification? Thanks for any pointers :) Jerry ---(end of broadcast)--- TIP 4: Have you searched our list archives? http://archives.postgresql.org/
Re: [GENERAL] Synchronize tables question....
On Feb 19, 2007, at 9:05 AM, Richard Huxton wrote:
Don't forget to CC: the list
Jerry LeVan wrote:
Is there an elegant way I can merge/update the two tables so that
they will contain the same information ( with no duplicates or
omissions)?
It sounds like you'll want some form of replication, but whether
single-master or multi-master no-one can say without more
information.
I meant to say I had dblink installed :)
The following sequence of steps seems to work ok, the tables are
very small...
insert into tmpRegistrations select *
from dblink('select * from registrations ')
as (software text,
id text,
value text,
location text
)
select dblink_disconnect()
create temp table newregistrations as
(select * from registrations union select * from
tmpregistrations )
truncate table registrations
insert into registrations select * from newregistrations
A couple of points:
1. What if a registration is updated?
2. What happens if you get a new registration between CREATE TEMP
TABLE and TRUNCATE?
--
Richard Huxton
Archonet Ltd
While a "generic" solution would be nice, I am the only one using the
DB :)
(so point 2 is unlikely).
Point 1 will require a bit of thought..., currently I would have to do
a manual scan of the (small) table after the merge.
Thanks
Jerry
---(end of broadcast)---
TIP 5: don't forget to increase your free space map settings
[GENERAL] Synchronize tables question....
Hi, I have a table with four text fields on two different machines that contain information about mail list passwords/software keys and similar information. Neither table has any keys or constraints. I do have dbi installed on each machine... Is there an elegant way I can merge/update the two tables so that they will contain the same information ( with no duplicates or omissions)? Thanks, Jerry ---(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
[GENERAL] Collating Question...
Hi, I am running 8.2.1 on my Mac OS X and my X86 Fedora Laptop... I just noticed that on my mac: levan=# select 'A' < 'a' ; ?column? -- t (1 row) and on the linux box: levan=# select 'A' < 'a' ; ?column? -- f (1 row) The locale function on the mac has everything set to "C" and on the linux box it is all "en_US.UTF-8". Is there a simple way to get the collating sequences to be the same on both boxen? If I do an "order by " on the mac then if the referenced field starts with a lower case letter then it will appear after all of the fields that start with an upper case letter Thanks, Jerry ---(end of broadcast)--- TIP 2: Don't 'kill -9' the postmaster
[GENERAL] Ann: PyPgExplorer-0.8
PyPgExplorer is a pure python application that allows the user to browse and modify Postgresql Databases. Features include: o A Scripts menu that makes access to your favorite SQL scripts only a click away. o On unix and Mac systems, if psql is detected in a standard location, then access to this tool is exposed in PyPgExplorer. o If the PIL module is available then bytea fields containing images can be viewed (in a separate window) in PyPgExplorer. o Fields in the database can be exported to the users file system. o PyPgExplorer supports a simple editor. The editor can be used to update/delete/insert records. The editor also supports importing BYTEA (think images) data from files into the database. Should work in Mac OSX, Linux, WinXP. Documentation, requirements and Source freely available at: http://homepage.mac.com/levanj/Python My homepage: http://homepage.mac.com/levanj This is by no means a PGAdmin replacement :) Thanks Jerry ---(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: [GENERAL] psql for winxp?
Hi John, Is it possible to have the installer only emplace psql and the necessary support libs? Jerry On Jun 19, 2006, at 8:36 PM, John DeSoi wrote: Hi Jerry, You can use psql directly and communicate with it using a pipe stream. On Windows I believe this is equivalent to calling CreateProcess and CreatePipe which results in a bidirectional stream. This is how pgEdit makes use of psql for the editor. I'm not familiar with Tcl or Python, but hopefully they have facilities to do this. BTW, the psql binary is part of the Windows PostgreSQL installer. On Jun 19, 2006, at 5:53 PM, Jerry LeVan wrote: I would like to install a "psql" command line program on my winxp box. ( something that acts like psql on a unix box.) I hope to embed such a program in my Tcl/Tk and Python PostgreSQL browsers so I can more offer more functionality in the browsers... My development environment on XP is restricted to scripting languages ( tcl and python ). Any candidates/suggestions? John DeSoi, Ph.D. http://pgedit.com/ Power Tools for PostgreSQL ---(end of broadcast)--- TIP 2: Don't 'kill -9' the postmaster
[GENERAL] psql for winxp?
Hi, I would like to install a "psql" command line program on my winxp box. ( something that acts like psql on a unix box.) I hope to embed such a program in my Tcl/Tk and Python PostgreSQL browsers so I can more offer more functionality in the browsers... My development environment on XP is restricted to scripting languages ( tcl and python ). Any candidates/suggestions? Jerry ---(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: [GENERAL] Mac Problem with Tunneling...
On May 13, 2006, at 6:18 PM, Tom Lane wrote: Jerry LeVan <[EMAIL PROTECTED]> writes: How ever if I turn it around, and on the mac issue the command ssh -L :linuxbox:5432 -l jerry linuxbox Then I am not able to connect to the linux box via psql or any Gui front ends. [ tries it ... ] Worksforme, using the stock ssh in OS X 10.4.6. Maybe you've got the OS X firewall configured to prevent connections to port ? That doesn't seem to be default, because I didn't have to adjust the firewall for my experiment. Another possibility is that the ssh daemon on the linux box is restricted from opening local connections. It wouldn't surprise me if this is disabled by default by SELinux for instance :-( regards, tom lane I am still puzzled. I don't think it is a postgresql problem since I can't forward to other daemons running on the linux box. I have noticed a error in the message file on the linux box that is generated when ever I try to connect from the mac. ** debug1: Connection to port 2224 forwarding to linuxbox port 2224 requested. debug2: fd 9 setting TCP_NODELAY debug2: fd 9 is O_NONBLOCK debug2: fd 9 is O_NONBLOCK debug1: channel 3: new [direct-tcpip] channel 3: open failed: administratively prohibited: open failed debug1: channel 3: free: direct-tcpip: listening port 2224 for linuxbox port 2224, connect from ::1 port 50663, nchannels 4 debug3: channel 3: status: The following connections are open: #2 client-session (t4 r0 i0/0 o0/0 fd 6/7) #3 direct-tcpip: listening port 2224 for linuxbox port 2224, connect from ::1 port 50663 (t3 r-1 i0/0 o0/0 fd 9/9) debug3: channel 3: close_fds r 9 w 9 e -1 May 13 19:22:05 localhost sshd[5844]: error: connect_to linuxbox: unknown host (Name or service not known) *** It appears that I have to somehow tell the linux box about the Mac This does not appear to be necessary when talking to the mac from the linux box. Sigh, Jerry ---(end of broadcast)--- TIP 6: explain analyze is your friend
[GENERAL] Mac Problem with Tunneling...
Hi, On my linux box I can issue the command ssh -L :macjerry:5432 -l jerry macjerry This will create a "tunnel" to connect to my mac named "macjerrry". I can connect to databases on macjerry via psql by specifying port on my linux box and other postgresql front ends. How ever if I turn it around, and on the mac issue the command ssh -L :linuxbox:5432 -l jerry linuxbox Then I am not able to connect to the linux box via psql or any Gui front ends. I get an error: [EMAIL PROTECTED] ~]$ channel 3: open failed: administratively prohibited: open failed channel 3: open failed: administratively prohibited: open failed No errors appear in the server log on the linux box. I am new to ssh, have I overlooked something? Jerry ---(end of broadcast)--- TIP 5: don't forget to increase your free space map settings
Re: [GENERAL] convert LO to BYTEA
Markus, PgBrowse 1.7a allows saving Large Objects into a file and the PgBrowse editor also allows inserting Bytea Fields from a file. See http://homepage.mac.com/levanj/TclTk Jerry ---(end of broadcast)--- TIP 4: Have you searched our list archives? http://archives.postgresql.org
Re: [GENERAL] "save history" problem
David, It appears that the problem is related to the fact that MacOSX does not really use the libreadline (checks and you will see that it is a symlink to libedit.) I asked this question a year or so ago and Tom Lane said that when the history file was closed that the libedit did not return the right status code. I got rid of the error message by changing the source to ignore the return code... Currently I simply ignore the error message :) and use tools that have reduced my usage of psql to a bare minimum. ( http://homepage.mac.com/levanj ) Jerry ---(end of broadcast)--- TIP 6: explain analyze is your friend
[GENERAL] MediaWiki and Postgresql?
The propaganda at MediaWiki is sorta vague on Postgresql support. Has anyone put MediaWiki up using the current version of Postgresql? Jerry ---(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: [GENERAL] Postgresql won't run after upgrade to fc5
I copied over the missing libs from one of my other fc4 systems and postgresql seems happy and I have not experienced any other problems so far... Jerry On Mar 21, 2006, at 11:46 PM, Bruno Wolff III wrote: On Wed, Mar 22, 2006 at 00:10:53 +0200, Devrim GUNDUZ <[EMAIL PROTECTED]> wrote: Hi, On Tue, 2006-03-21 at 17:02 -0500, Jerry LeVan wrote: I accidently upgraded my linux/intel to fc5 from fc4 and something happened... Postgres cannot find some needed shared libraries any more. We (PGDG) don't have RPMs for FC5 yet. However Fedora Core ships with 8.1.3 RPMs already. So I'd install their RPMs. This should not cause a problem since the database versions are the same. I wouldn't trust that if I didn't have to. FC5 is using a different version of gcc than FC4. In addition they might have used different build options than the PGDG did. ---(end of broadcast)--- TIP 6: explain analyze is your friend
Re: [GENERAL] Postgresql won't run after upgrade to fc5
Hmmm, It appears that they bumped libcryto and libssl (living in /lib ) by a smidgen. I might try moving the old versions from an existing fc4 over to fc5. If that does not work then I guess I will need to uninstall the PGDG rpms and install the FC5 rpms. Thanks Jerry On Mar 21, 2006, at 5:10 PM, Devrim GUNDUZ wrote: Hi, On Tue, 2006-03-21 at 17:02 -0500, Jerry LeVan wrote: I accidently upgraded my linux/intel to fc5 from fc4 and something happened... Postgres cannot find some needed shared libraries any more. We (PGDG) don't have RPMs for FC5 yet. However Fedora Core ships with 8.1.3 RPMs already. So I'd install their RPMs. This should not cause a problem since the database versions are the same. Regards, -- The PostgreSQL Company - Command Prompt, Inc. 1.503.667.4564 PostgreSQL Replication, Consulting, Custom Development, 24x7 support Managed Services, Shared and Dedicated Hosting Co-Authors: PL/php, plPerlNG - http://www.commandprompt.com/ ---(end of broadcast)--- TIP 4: Have you searched our list archives? http://archives.postgresql.org
[GENERAL] Postgresql won't run after upgrade to fc5
Hi, I accidently upgraded my linux/intel to fc5 from fc4 and something happened... Postgres cannot find some needed shared libraries any more. Can anyone offer any clues? Jerry /usr/bin/postmaster: error while loading shared libraries: libssl.so.5: cannot open shared object file: No such file or directory [EMAIL PROTECTED] lib]# rpm -qa | grep postgres postgresql-tcl-8.1.3-1PGDG postgresql-server-8.1.3-1PGDG postgresql-python-8.1.3-1PGDG postgresql-docs-8.1.3-1PGDG postgresql-libs-8.1.3-1 postgresql-jdbc-8.1.3-1PGDG postgresql-contrib-8.1.3-1PGDG postgresql-devel-8.1.3-1PGDG postgresql-8.1.3-1PGDG postgresql-pl-8.1.3-1PGDG [EMAIL PROTECTED] bin]$ ldd postgres linux-gate.so.1 => (0x00d07000) libpam.so.0 => /lib/libpam.so.0 (0x004d9000) libssl.so.5 => not found libcrypto.so.5 => not found libkrb5.so.3 => /usr/lib/libkrb5.so.3 (0x00571000) libz.so.1 => /usr/lib/libz.so.1 (0x00839000) libreadline.so.5 => /usr/lib/libreadline.so.5 (0x00a5b000) libtermcap.so.2 => /lib/libtermcap.so.2 (0x00eb4000) libcrypt.so.1 => /lib/libcrypt.so.1 (0x008a8000) libresolv.so.2 => /lib/libresolv.so.2 (0x00111000) libnsl.so.1 => /lib/libnsl.so.1 (0x00959000) libdl.so.2 => /lib/libdl.so.2 (0x00124000) libm.so.6 => /lib/libm.so.6 (0x0038f000) libc.so.6 => /lib/libc.so.6 (0x00128000) libcom_err.so.2 => /lib/libcom_err.so.2 (0x00c8c000) libaudit.so.0 => /lib/libaudit.so.0 (0x0025b000) libk5crypto.so.3 => /usr/lib/libk5crypto.so.3 (0x00988000) /lib/ld-linux.so.2 (0x00cb9000) libkrb5support.so.0 => /usr/lib/libkrb5support.so.0 (0x00d54000) [EMAIL PROTECTED] lib]# ls -al libcrypto* -rw-r--r-- 1 root root 2320564 Feb 12 03:33 libcrypto.a lrwxrwxrwx 1 root root 29 Mar 21 09:00 libcrypto.so -> ../../lib/ libcrypto.so.0.9.8a [EMAIL PROTECTED] lib]# ls -al libssl* -rw-r--r-- 1 root root 706805 Feb 15 02:41 libssl3.so -rw-r--r-- 1 root root 439208 Feb 12 03:33 libssl.a lrwxrwxrwx 1 root root 26 Mar 21 09:00 libssl.so -> ../../lib/ libssl.so.0.9.8a ---(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
[GENERAL] ANN: PgBrowser-1.6 and PgBrowser-1.7
PgBrowse ver 1.7 is a generic Postgresql database browser that works on Windows, Macintosh and Linux platforms that is written in Tcl/Tk. A Starpack is available for Linux/x86 and an application bundle is available for MacOSX. What is new in 1.6? o 1.6 Contains and can display the complete html Postgresql documentation set. What is new in 1.7? o Corrected error that prevented "Postgresql Documentation" from being opened more than once per session. (sigh...) o Added the ability to save the contents of the SQL window. By default the saved file will have an extension of ".sql" and will be written to the "~/SQLScripts" directory. o Added the ability to refresh the scripts menu while the program is running. o Added MouseWheel support (each event scrolls 5 units). A some features of PgBrowser. 1) PgBrowser can display/extract graphical images stored in the database as bytea or large objects (via the Img package). 2) PgBrower supports SQL libraries of your favorite queries. At startup PgBrowser looks for "~/SQLScripts" and builds a menu of all members of the directory that end in ".sql". Subdirectories will generate the appropriate submenu. Selecting a menu item will load the SQL window with the query. 3) PgBrowser supports a "history" of queries/commands passed to the backend. Previous commands can be easily recalled from the keyboard. Gracefully exiting the program will cause the history to be stored in "~/SQLScripts" as HiStOrY.tcl. This file will be "sourced" at program startup to recover the command history. 4) If PgBrowser is running on a Mac or Linux system that has "psql" located in a standard location, it is possible to execute "psql" commands from within PgBrowser. 5) Individual fields can be extracted and saved to user specified files. This includes bytea and large object fields. 6) A simple grid based table editor is now available to make changes in the database. The editor has features that facilitate the use of BYTEA and Large Object fields. For more information and download visit: http://homepage.mac.com/levanj/TclTk Suggestions for improvements and bug fixes gladly accepted. Thanks, Jerry ---(end of broadcast)--- TIP 2: Don't 'kill -9' the postmaster
[GENERAL] Funky template1 problem?
Hi, I have a bunch of small dbs (levan, pictures, and a couple of others). I have had these db's over many upgrades and I have just noticed that template1 seems to be a bit munged... testuser=> \c template1 You are now connected to database "template1". template1=> \d List of relations Schema | Name | Type | Owner ++--+--- public | lo_shadow | table| levan public | my_description | table| levan public | person | table| levan public | person_id_seq | sequence | levan public | pics | table| levan public | pics_ident_seq | sequence | levan (6 rows) This is the same as... template1=> \c pictures You are now connected to database "pictures". pictures=> \d List of relations Schema | Name | Type | Owner ++--+--- public | lo_shadow | table| levan public | my_description | table| levan public | person | table| levan public | person_id_seq | sequence | levan public | pics | table| levan public | pics_ident_seq | sequence | levan (6 rows) I found this out when I tried to create a new user testuser for testing a totally none privileged user. When I recreate the testuser db using template1 I found the tables from the picture db were in the newly created db. Is it safe to simple drop the db's from the template1 db? ( I have no idea of how the tables became part of template1.) Jerry ---(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
[GENERAL] ANN: PgBrowse 1.5
(Sorry for the spam but pgsql-announce refuses to recognize my mail..._ PgBrowse ver 1.5 is a generic Postgresql database browser that works on Windows, Macintosh and Linux platforms that is written in Tcl/Tk. A Starpack is available for Linux/x86 and an application bundle is available for MacOSX. What is new in 1.5? o Fixed a bug where columns having uppercase letters in their name were not processed correctly in the editor. o Added a "reserved" word LOBJ. If LOBJ appears in the buffer area of the editor then clicking the update/insert button will open a file selector box and the user can select a file that will be inserted into the database as a large object. The oid of the created object will be placed into the users table corresponding to the column where LOBJ appeared. The user will be given a chance to rollback/commit the action. A couple of features that help differentiate this (free) tool. 1) No postresql software is actually needed on the client. 2) PgBrowser can display graphical images stored in the database as bytea or large objects (via the Img package). 3) PgBrower supports SQL libraries of your favorite queries. At startup PgBrowser looks for "~/SQLScripts" and builds a menu of all members of the directory that end in ".sql". Subdirectories will generate the appropriate submenu. Selecting a menu item will load the SQL window with the query. 4) PgBrowser supports a "history" of queries/commands passed to the backend. Previous commands can be easily recalled from the keyboard. Gracefully exiting the program will cause the history to be stored in "~/SQLScripts" as HiStOrY.tcl. This file will be "sourced" at program startup to recover the command history. 5) If PgBrowser is running on a Mac or Linux system that has "psql" located in a standard location, it is possible to execute "psql" commands from within PgBrowser. 6) Individual fields can be extracted and saved to user specified files. This includes bytea and large object fields. 7) A simple grid based table editor is now available to make changes in the database. The editor has features that facilitate the use of BYTEA and Large Object fields. For more information and download visit: http://homepage.mac.com/levanj/TclTk Suggestions for improvements and bug fixes gladly accepted. Thanks, Jerry ---(end of broadcast)--- TIP 2: Don't 'kill -9' the postmaster
Re: [GENERAL] Installing the latest 8.1.1 rpms question.
On Dec 14, 2005, at 3:15 AM, Richard Huxton wrote: Jerry LeVan wrote: Hi, I just downloaded the 8.1.1 rpms for FC4 from postgresql.org. It appears that removing the existing rpms will require also removing a number of dependencies. (That what Synaptics asserts...) Is it possible to use a "rpm -Uvh *" to overwrite the existing 8.1.0 rpms from postgresql.org? and not have to reload all of the other bits and pieces? That should work just fine. You shouldn't need to dump/reload either, although I always do where possible. Don't forget when 8.2 comes out and you want to upgrade you will NEED to pg_dump your data first and then restore it. -- Richard Huxton Archonet Ltd Oh well, I chickened out and rm'ed the existing rpms and noted which dependencies were deleted via pencil and paper. I then installed the new rpms and reinstalled the previous dependencies. I think it probably took less time to build and install from source on my mac than going with the rpm route :) Thanks, Jerry ---(end of broadcast)--- TIP 4: Have you searched our list archives? http://archives.postgresql.org
[GENERAL] ANN: PgBrowse 1.4
PgBrowse ver 1.4 is a generic Postgresql database browser that works on Windows, Macintosh and Linux platforms that is written in Tcl/Tk. A Starpack is available for Linux/x86 and an application bundle is available for MacOSX. What is new in 1.4? o Fixed a bug where fields greater than 200 characters could not be edited. o Added the ability to insert or update bytea fields in the editor. If the edit buffer contains the unquoted word BYTEA for the value of a column then when an UPDATE or INSERT is done the program will allow the user to select a file to be used as the contents of the field. A couple of features that help differentiate this (free) tool. 1) No postresql software is actually needed on the client. 2) PgBrowser can display graphical images stored in the database as bytea or large objects (via the Img package). 3) PgBrower supports SQL libraries of your favorite queries. At startup PgBrowser looks for "~/SQLScripts" and builds a menu of all members of the directory that end in ".sql". Subdirectories will generate the appropriate submenu. Selecting a menu item will load the SQL window with the query. 4) PgBrowser supports a "history" of queries/commands passed to the backend. Previous commands can be easily recalled from the keyboard. Gracefully exiting the program will cause the history to be stored in "~/SQLScripts" as HiStOrY.tcl. This file will be "sourced" at program startup to recover the command history. 5) If PgBrowser is running on a Mac or Linux system that has "psql" located in a standard location, it is possible to execute "psql" commands from within PgBrowser. 6) Individual fields can be extracted and saved to user specified files. This includes bytea and large object fields. 7) A simple grid based table editor is now available to make changes in the database. For more information and download visit: http://homepage.mac.com/levanj/TclTk Suggestions for improvements and bug fixes gladly accepted. Thanks, Jerry ---(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
[GENERAL] Installing the latest 8.1.1 rpms question.
Hi, I just downloaded the 8.1.1 rpms for FC4 from postgresql.org. It appears that removing the existing rpms will require also removing a number of dependencies. (That what Synaptics asserts...) Is it possible to use a "rpm -Uvh *" to overwrite the existing 8.1.0 rpms from postgresql.org? and not have to reload all of the other bits and pieces? Jerry ---(end of broadcast)--- TIP 5: don't forget to increase your free space map settings
[GENERAL] OpenOffice 2 and Postgresql 8.1 How to?
Are there any (detailed) instructions available on how to connect OpenOffice 2 and Postgresql 8.1. I have the jdbc driver(s) from postgresql.org... I am running FC4 and have access to DB's on a Mac and the Linux box. Thanks, Jerry ---(end of broadcast)--- TIP 6: explain analyze is your friend
Re: [GENERAL] Update and bytea problem...
Begin forwarded message: From: Jerry LeVan <[EMAIL PROTECTED]> Date: December 9, 2005 10:45:35 PM EST To: Michael Fuhr <[EMAIL PROTECTED]> Cc: Postgres General Subject: Re: [GENERAL] Update and bytea problem... On Dec 9, 2005, at 9:35 PM, Michael Fuhr wrote: On Fri, Dec 09, 2005 at 08:46:17PM -0500, Jerry LeVan wrote: I am trying to write a general update command where there might be "bytea" fields involved. The update command is generated programatically. I am having some problems when a bytea field is involved. What language are you using and how are you escaping the bytea data? Could you post a code snippet so we can see exactly what you're doing? -- Michael Fuhr Sigh, it is really messy, I am writing in Tcl and using Pgtcl as the interface to Postgresql. This seems to work ok: insert into pics byteafield='' I have been able to extract the byteafield and get the original file contents , jpg, png, etc...maybe I have been lucky? However update pics set byteafield='' where byteafield='' has always failed for me unless the "other pg_escaped string" is a simple string. probably when pg_escaped string == string. Assuming I am not overlooking something obvious, I wonder how the "where clause" above is evaluated for bytea columns... do I need to unpgescape the string and then pg quote it? Something is not clear to me: I notice that pg_escaped strings can contain "'s are floating about in pg_escaped strings... Back to manuals... Jerry Hmmm, This seems to work... update pic set byteafield='' where byteafield = pg_quote ( Still gotta do more testing. Tain't clear why I don't have to pg_quote the in the set clause... Jerry ---(end of broadcast)--- TIP 4: Have you searched our list archives? http://archives.postgresql.org
Re: [GENERAL] Update and bytea problem...
On Dec 9, 2005, at 9:35 PM, Michael Fuhr wrote: On Fri, Dec 09, 2005 at 08:46:17PM -0500, Jerry LeVan wrote: I am trying to write a general update command where there might be "bytea" fields involved. The update command is generated programatically. I am having some problems when a bytea field is involved. What language are you using and how are you escaping the bytea data? Could you post a code snippet so we can see exactly what you're doing? -- Michael Fuhr Sigh, it is really messy, I am writing in Tcl and using Pgtcl as the interface to Postgresql. This seems to work ok: insert into pics byteafield='' I have been able to extract the byteafield and get the original file contents , jpg, png, etc...maybe I have been lucky? However update pics set byteafield='' where byteafield='' has always failed for me unless the "other pg_escaped string" is a simple string. probably when pg_escaped string == string. Assuming I am not overlooking something obvious, I wonder how the "where clause" above is evaluated for bytea columns... do I need to unpgescape the string and then pg quote it? Something is not clear to me: I notice that pg_escaped strings can contain "'s are floating about in pg_escaped strings... Back to manuals... Jerry ---(end of broadcast)--- TIP 5: don't forget to increase your free space map settings
[GENERAL] Update and bytea problem...
Hi, I am trying to write a general update command where there might be "bytea" fields involved. The update command is generated programatically. I am having some problems when a bytea field is involved. A generated command might look like: update pics set info='moof.jpg', byteafield='moof.jpg>' where info='doofus.jpg' and byteafield = 'doofus.jpg>' Unfortunately the above does not seem to work, I keep getting a syntax error with an invalid character '\' generally thousands of bytes into the command. Does update play nice with bytea used as above ( the escaped contents of doofus.jpg are the results of fetching the byteafield as text...)? For a couple of reasons ( NULL and DEFAULT) I have to use a text interface. Thanks Jerry ---(end of broadcast)--- TIP 3: Have you checked our extensive FAQ? http://www.postgresql.org/docs/faq
[GENERAL] I can't build the 8.1.0 source rpm from postgresql.org
I downloaded the postgresql-8.1.0 source rpm for Fedora Core 4 from the rpm repository at postgresql.org. I installed the rpm with " rpm -i postgresql-8.1.0-2PGDG.src.rpm" I then attempted to rebuild the packages with rpmbuild --rebuild --define 'tcl 1' --define 'kerberos 0' --define 'tcldevel 1' \ --define 'pltcl 1' postgresql-8.1.0 It appears to die in the prep stage: ++ basename /usr/src/redhat/SOURCES/pgtcldocs-20041108.zip .zip + PGTCLDOCDIR=pgtcldocs-20041108 + mv pgtcldocs-20041108 Pgtcl-docs + echo 'Patch #5 (pgtcl-no-rpath.patch):' Patch #5 (pgtcl-no-rpath.patch): + patch -p0 -s + pushd Pgtcl /usr/src/redhat/BUILD/postgresql-8.1.0/Pgtcl /usr/src/redhat/BUILD/ postgresql-8.1.0 + %aconfver /var/tmp/rpm-tmp.58757: line 79: fg: no job control error: Bad exit status from /var/tmp/rpm-tmp.58757 (%prep) RPM build errors: InstallSourcePackage: Header V3 DSA signature: NOKEY, key ID 748f7d0e user devrim does not exist - using root group devrim does not exist - using root user devrim does not exist - using root group devrim does not exist - using root Bad exit status from /var/tmp/rpm-tmp.58757 (%prep) Any suggestions? Jerry ---(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
[GENERAL] ANN: PgBrowse-1.3 is available.
PgBrowse ver 1.3 is a generic Postgresql database browser that works on Windows, Macintosh and Linux platforms that is written in Tcl/Tk. A Starpack is available for Linux/x86 and an application bundle is available for MacOSX. A couple of features that help differentiate this (free) tool. 1) No postresql software is actually needed on the client. 2) PgBrowser can display graphical images stored in the database as bytea or large objects (via the Img package). 3) PgBrower supports SQL libraries of your favorite queries. At startup PgBrowser looks for "~/SQLScripts" and builds a menu of all members of the directory that end in ".sql". Subdirectories will generate the appropriate submenu. 4) PgBrowser supports a "history" of queries/commands passed to the backend. Previous commands can be easily recalled from the keyboard. Gracefully exiting the program will cause the history to be stored in "~/SQLScripts" as HiStOrY.tcl. This file will be "sourced" at program startup to recover the command history. 5) If PgBrowser is running on a Mac or Linux system that has "psql" located in a standard location, it is possible to execute "psql" commands from within PgBrowser. 6) Individual fields can be extracted and saved to user specified files. This includes bytea and large object fields. 7) A simple grid based database table editor is now available to make changes in the database. For more information and download visit: http://homepage.mac.com/levanj/TclTk Suggestions for improvements and bug fixes gladly accepted. Thanks, Jerry ---(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: [GENERAL] Tcl Support in the FC4 rpms at posgresql.org?
Hmm.
The "--rebuild" option is not recognized by the default rpm supplied
with FC4.
There is an rpmbuild command, but it always appears to do an "install".
Is there any way to simply build the binary rpms from the postgresql
src rpm
without doing an "install"?
Browsing about, I found the PostgreSQL-RPM-installation-PGDG.pdf
file. The
packages that it asserts will be build seem a bit different from what is
in the spec file.
In any case, from which directory should the rpmbuild command be given?
Thanks,
Jerry
On Nov 27, 2005, at 2:07 PM, Devrim GUNDUZ wrote:
Hi,
On Sun, 27 Nov 2005, Jerry LeVan wrote:
Is Tcl support included in any of the FC4 rpms located
at postgresql.org? { I am talking about the 8.1 release }.
No.
If you need the tcl rpm, you need to rebuild our srpm:
rpm --rebuild --define 'tcl 1' postgresql-8.1.0-2PGDG.src.rpm
Regards,
--
Devrim GUNDUZ
Kivi Bilişim Teknolojileri - http://www.kivi.com.tr
devrim~gunduz.org, devrim~PostgreSQL.org, devrim.gunduz~linux.org.tr
http://www.gunduz.org
---(end of broadcast)---
TIP 4: Have you searched our list archives?
http://archives.postgresql.org
[GENERAL] Tcl Support in the FC4 rpms at posgresql.org?
Is Tcl support included in any of the FC4 rpms located
at postgresql.org? { I am talking about the 8.1 release }.
(Tain't clear from the names of the rpms...)
If tcl support is in one of the rpms then does
the install proceed by downloading all of the
rpms into a single directory and then issue
a magic rpm command to install all at once.
( I assume I will have to delete all of the
older postgresql rpms prior to the new install...)
Failing that...
If I download the src rpm then what are the
magical rpm incantations that that will build
the whole shebang and then install the rascal.
I am new to linux and don't especially like the
way the linux fc4 distribution seems to scatter
the files all over the place...Can I assume that
the src rpm puts the files where ever they are
supposed to go?
Jerry
---(end of broadcast)---
TIP 3: Have you checked our extensive FAQ?
http://www.postgresql.org/docs/faq
[GENERAL] Default and PQexecParams
Hi, How could one differentiate between DEFAULT and 'DEFAULT' as parameters to PQexecuteParams? Jerry ---(end of broadcast)--- TIP 4: Have you searched our list archives? http://archives.postgresql.org
[GENERAL] Cursors or Offset, Limit?
Hi, I am mucking around trying to build a gui'sh "table editor" for Postgresql. I am currently using a "held" cursor to move around the table, Since the "cursor" does not show table modification I am thinking about using the "limit" and "offset" attributes to select the rows to display. What are some of the tradeoffs between using a cursor and using the limit/offset method of selecting rows to display? Thanks, Jerry ---(end of broadcast)--- TIP 3: Have you checked our extensive FAQ? http://www.postgresql.org/docs/faq
Re: [GENERAL] psql error on quitting...
Tom was right, on the Mac libreadline is linked to libedit. My "solution" was to comment out the line reporting the error in the program "input.c" Jerry On Nov 9, 2005, at 7:27 AM, Andreas Seltenreich wrote: Tom Lane writes: Jerry LeVan <[EMAIL PROTECTED]> writes: I just upgraded from 8.0.4 to 8.1.0 this afternoon and the only thing "bad" I have noticed is that whenever I quit psql I get a message: could not save history to file "/Users/jerry/.psql_history": Invalid argument This is on MacOS X 10.4.3 The Postgres code in that area hasn't changed at all. input.c has: --8<---cut here---start->8--- revision 1.45 date: 2005/06/10 15:40:41; author: momjian; state: Exp; lines: +2 -2 Use saveHistory so we get a nice error message on failure. --8<---cut here---end--->8--- So, the error probably also occured in 8.0.4, but just wasn't reported at all. regards, Andreas ---(end of broadcast)--- TIP 3: Have you checked our extensive FAQ? http://www.postgresql.org/docs/faq
[GENERAL] psql error on quitting...
Hi, I just upgraded from 8.0.4 to 8.1.0 this afternoon and the only thing "bad" I have noticed is that whenever I quit psql I get a message: could not save history to file "/Users/jerry/.psql_history": Invalid argument This is on MacOS X 10.4.3 Thanks for any info... Jerry ---(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: [GENERAL] psql error on quitting...
Some more info, the history is actually written! ( ' ' seems to be translated to \40 ) Still get the error message... Jerry Subject: psql error on quitting... Hi, I just upgraded from 8.0.4 to 8.1.0 this afternoon and the only thing "bad" I have noticed is that whenever I quit psql I get a message: could not save history to file "/Users/jerry/.psql_history": Invalid argument This is on MacOS X 10.4.3 Thanks for any info... Jerry ---(end of broadcast)--- TIP 2: Don't 'kill -9' the postmaster
[GENERAL] Ann: PgBrowser-1.1
PgBrowse ver 1.1 is a generic Postgresql database browser that works on Windows, Macintosh and Linux platforms that is written in Tcl/Tk. A couple of features that help differentiate this (free) product. 1) No postresql software is actually needed on the client. ( but both functionality and speed will suffer). 2) PgBrowser can display graphical images stored in the database as bytea or large objects (via the Img package). 3) PgBrower supports SQL libraries of your favorite queries. At startup PgBrowser looks for "~/SQLScripts" and builds a menu of all members of the directory that end in ".sql". Subdirectories will generate the appropriate submenu. 4) PgBrowser supports a "history" of queries/commands passed to the backend. Previous commands can be easily recalled from the keyboard. Gracefully exiting the program will cause the history to be stored in "~/SQLScripts" as HiStOrY.tcl. This file will be "sourced" at program startup to recover the command history. 5) If PgBrowser is running on a Mac or Linux system that has "psql" located in a standard location, it is possible to execute "psql" commands from within PgBrowser. For more information and download visit: http://homepage.mac.com/levanj/TclTk Suggestions for improvements and bug fixes gladly accepted. Thanks, Jerry ---(end of broadcast)--- TIP 5: don't forget to increase your free space map settings
