[pgadmin-support] Bug with passwords that include apostrophes
pgAdmin version: latest bundled
OS: Windows XP
Description
---
Attempting to log into a database with pgAdmin using a password that
contains the apostrophe (') character causes this error:
"An error has occurred.
Error connecting to the server: missing "=" after "asdf" in connection
info string."
It's almost certain you have the same problem connecting with a username
with an apostrophe, or to a db name with one.
In the connection string you need to go:
password='asdf\'fdsa' dbname='dbname'
To properly escape it.
Chris
---(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: [pgadmin-support] Bug with passwords that include apostrophes
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf Of
> Christopher Kings-Lynne
> Sent: 16 June 2006 03:29
> To: pgadmin-support@postgresql.org
> Subject: [pgadmin-support] Bug with passwords that include apostrophes
>
> pgAdmin version: latest bundled
> OS: Windows XP
>
> Description
> ---
>
> Attempting to log into a database with pgAdmin using a password that
> contains the apostrophe (') character causes this error:
>
Latest bundled with what? That bug was fixed already:
2006-02-17 DP 1.4.2 Properly escape single quotes in connection
strings.
Regards, Dave.
---(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: [pgadmin-support] Bug with passwords that include apostrophes
Latest bundled with what? That bug was fixed already: 2006-02-17 DP 1.4.2 Properly escape single quotes in connection strings. Ah bummer. Turns out I had 1.4.0... Chris ---(end of broadcast)--- TIP 2: Don't 'kill -9' the postmaster
Re: [pgadmin-support] init script for redhat
I have attached a small patch to the Redhat pgagent init script to use the new log to file options. Cheers Jeremy > -Original Message- > From: Dave Page [mailto:[EMAIL PROTECTED] > Sent: Friday, 16 June 2006 12:54 a.m. > To: Jeremy Palmer; pgadmin-support@postgresql.org > Subject: RE: [pgadmin-support] init script for redhat > > Thanks, patch applied! > > Regards, Dave. > > > -Original Message- > > From: Jeremy Palmer [mailto:[EMAIL PROTECTED] > > Sent: 15 June 2006 13:20 > > To: Dave Page; pgadmin-support@postgresql.org > > Subject: RE: [pgadmin-support] init script for redhat > > > > Ok, thanks for the tips. I have attached an updated patch. > > > > Cheers > > Jeremy > > > > > -Original Message- > > > From: Dave Page [mailto:[EMAIL PROTECTED] > > > Sent: Friday, 16 June 2006 12:09 a.m. > > > To: Jeremy Palmer; pgadmin-support@postgresql.org > > > Subject: RE: [pgadmin-support] init script for redhat > > > > > > > > > > > > > -Original Message- > > > > From: Jeremy Palmer [mailto:[EMAIL PROTECTED] > > > > Sent: 15 June 2006 12:59 > > > > To: Dave Page; pgadmin-support@postgresql.org > > > > Subject: RE: [pgadmin-support] init script for redhat > > > > > > > > Hi Dave, > > > > > > > > Attached is a patch that allows pgagent to immediately log > > > > messages to file. > > > > I have tentatively changed the cmd line switch for logging > > > > verbosity to "-s" > > > > so "-l" can be used for the log file specification. I felt > > > > that this was > > > > more intuitive. > > > > > > > > If the patch is accepted, then a small change to the init > > > > script will need > > > > to be made to accommodate the file logging... > > > > > > Hi Jeremy, > > > > > > Looks good - just a couple of points... > > > > > > - Strings that are candidates for translation (when added > > to pgAgent) > > > should be wrapped in the _() macro, not wxT(); for example, > > your 'cannot > > > open the logfile' string. > > > > > > - Changing the command line options is unnacceptable except > > in extreme > > > cases because it can easily confuse people when upgrading, > > expecially if > > > they miss the change. Please use -l for the loglevel as per current > > > releases and choose another letter for the logfile. > > > > > > Thanks, Dave. > > pgagent_init.patch Description: Binary data ---(end of broadcast)--- TIP 6: explain analyze is your friend
[pgadmin-support] Postgis Manual
Hi guys, I was wondering if it was possible to get the postgis manual added into the pgadmin3 help. This would be really useful for a few guys at work as we always need to refer to the postgis function section, and it would be great if it was integrated into pgadmin3! The postgis manual is a dockbook, so making html pages or html help workshop files should be easy enough... Thanks Jeremy ---(end of broadcast)--- TIP 3: Have you checked our extensive FAQ? http://www.postgresql.org/docs/faq
Re: [pgadmin-support] Postgis Manual
> -Original Message- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of > Jeremy Palmer > Sent: 16 June 2006 10:42 > To: pgadmin-support@postgresql.org > Subject: [pgadmin-support] Postgis Manual > > Hi guys, > > I was wondering if it was possible to get the postgis manual > added into the > pgadmin3 help. This would be really useful for a few guys at > work as we > always need to refer to the postgis function section, and it > would be great > if it was integrated into pgadmin3! The postgis manual is a > dockbook, so > making html pages or html help workshop files should be easy enough... The problem is that updating an building the docs is the most time consuming and painful job there is for me to do at both pgAdmin and PostgreSQL release times. I'm *really* loathe to add another docset in there. It is on my longterm todo to see if we can't automate things a little more however, if you (or anyone else) is an HTMLHelp expert, then I'd love to hear ideas about how the index file hacking can be avoided - even just a way to #include index/contents files in a subdir without hacking the source paths for the html files to be relative to the top dir would be a big help. Regards, Dave. ---(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: [pgadmin-support] init script for redhat
Thanks, patch applied. Regards, Dave. > -Original Message- > From: Jeremy Palmer [mailto:[EMAIL PROTECTED] > Sent: 16 June 2006 10:32 > To: Dave Page; pgadmin-support@postgresql.org > Subject: RE: [pgadmin-support] init script for redhat > > I have attached a small patch to the Redhat pgagent init > script to use the > new log to file options. > > Cheers > Jeremy > > > -Original Message- > > From: Dave Page [mailto:[EMAIL PROTECTED] > > Sent: Friday, 16 June 2006 12:54 a.m. > > To: Jeremy Palmer; pgadmin-support@postgresql.org > > Subject: RE: [pgadmin-support] init script for redhat > > > > Thanks, patch applied! > > > > Regards, Dave. > > > > > -Original Message- > > > From: Jeremy Palmer [mailto:[EMAIL PROTECTED] > > > Sent: 15 June 2006 13:20 > > > To: Dave Page; pgadmin-support@postgresql.org > > > Subject: RE: [pgadmin-support] init script for redhat > > > > > > Ok, thanks for the tips. I have attached an updated patch. > > > > > > Cheers > > > Jeremy > > > > > > > -Original Message- > > > > From: Dave Page [mailto:[EMAIL PROTECTED] > > > > Sent: Friday, 16 June 2006 12:09 a.m. > > > > To: Jeremy Palmer; pgadmin-support@postgresql.org > > > > Subject: RE: [pgadmin-support] init script for redhat > > > > > > > > > > > > > > > > > -Original Message- > > > > > From: Jeremy Palmer [mailto:[EMAIL PROTECTED] > > > > > Sent: 15 June 2006 12:59 > > > > > To: Dave Page; pgadmin-support@postgresql.org > > > > > Subject: RE: [pgadmin-support] init script for redhat > > > > > > > > > > Hi Dave, > > > > > > > > > > Attached is a patch that allows pgagent to immediately log > > > > > messages to file. > > > > > I have tentatively changed the cmd line switch for logging > > > > > verbosity to "-s" > > > > > so "-l" can be used for the log file specification. I felt > > > > > that this was > > > > > more intuitive. > > > > > > > > > > If the patch is accepted, then a small change to the init > > > > > script will need > > > > > to be made to accommodate the file logging... > > > > > > > > Hi Jeremy, > > > > > > > > Looks good - just a couple of points... > > > > > > > > - Strings that are candidates for translation (when added > > > to pgAgent) > > > > should be wrapped in the _() macro, not wxT(); for example, > > > your 'cannot > > > > open the logfile' string. > > > > > > > > - Changing the command line options is unnacceptable except > > > in extreme > > > > cases because it can easily confuse people when upgrading, > > > expecially if > > > > they miss the change. Please use -l for the loglevel as > per current > > > > releases and choose another letter for the logfile. > > > > > > > > Thanks, Dave. > > > > ---(end of broadcast)--- TIP 2: Don't 'kill -9' the postmaster
Re: [pgadmin-support] Bug with passwords that include apostrophes
How do I get an email address removed from this list?
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Christopher
Kings-Lynne
Sent: Thursday, June 15, 2006 10:29 PM
To: pgadmin-support@postgresql.org
Subject: [pgadmin-support] Bug with passwords that include apostrophes
pgAdmin version: latest bundled
OS: Windows XP
Description
---
Attempting to log into a database with pgAdmin using a password that
contains the apostrophe (') character causes this error:
"An error has occurred.
Error connecting to the server: missing "=" after "asdf" in connection info
string."
It's almost certain you have the same problem connecting with a username
with an apostrophe, or to a db name with one.
In the connection string you need to go:
password='asdf\'fdsa' dbname='dbname'
To properly escape it.
Chris
---(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
---(end of broadcast)---
TIP 3: Have you checked our extensive FAQ?
http://www.postgresql.org/docs/faq
Re: [pgadmin-support] Postgis Manual
> -Original Message- > From: John Cole [mailto:[EMAIL PROTECTED] > Sent: 16 June 2006 16:11 > To: Dave Page; Jeremy Palmer; pgadmin-support@postgresql.org > Subject: RE: [pgadmin-support] Postgis Manual > > Dave, > How are you generating your help file? We use a xsl > stylesheet to convert > xhtml to docbook and from there generate the help project. > I'd be happy to > give you the stylesheet and our tool chain instructions. Hi John, The pgAdmin docs are maintained as HTML files, along with an HTML help project (hhp project file, hhk index file and hhc contents file). The PostgreSQL and Slony docs start out in SGML and are converted to individual HTML help projects using docbook & xsltproc. The difficult bit is merging them together. At the moment I manually merge the hhp, hhk and hhc files together, and adjust the paths as I go to allow for the fact that the slony and pg docs are in slony/ and pg/ directories relative to the pgadmin docs. Ideally, I'd like to be able to either automagically do the merge operation, or see if the files can be '#included' so that (for example) pgadmin.hhp includes something like: #include pg/postgresql.hhp #include slony/slony.hhp There is a way of doing that in HTMLHelp iirc, but it didn't like the fact the paths to the content files (*.html, *.gif etc) weren't relative to the top directory. I suspect the easiest answer is for a perl hacker to step forward and wave his or her wand, but I'm open to other suggestions :-) Regards, Dave. ---(end of broadcast)--- TIP 3: Have you checked our extensive FAQ? http://www.postgresql.org/docs/faq
Re: [pgadmin-support] Postgis Manual
Dave, How are you generating your help file? We use a xsl stylesheet to convert xhtml to docbook and from there generate the help project. I'd be happy to give you the stylesheet and our tool chain instructions. John Cole -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Dave Page Sent: Friday, June 16, 2006 5:08 AM To: Jeremy Palmer; pgadmin-support@postgresql.org Subject: Re: [pgadmin-support] Postgis Manual > -Original Message- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of > Jeremy Palmer > Sent: 16 June 2006 10:42 > To: pgadmin-support@postgresql.org > Subject: [pgadmin-support] Postgis Manual > > Hi guys, > > I was wondering if it was possible to get the postgis manual > added into the > pgadmin3 help. This would be really useful for a few guys at > work as we > always need to refer to the postgis function section, and it > would be great > if it was integrated into pgadmin3! The postgis manual is a > dockbook, so > making html pages or html help workshop files should be easy enough... The problem is that updating an building the docs is the most time consuming and painful job there is for me to do at both pgAdmin and PostgreSQL release times. I'm *really* loathe to add another docset in there. It is on my longterm todo to see if we can't automate things a little more however, if you (or anyone else) is an HTMLHelp expert, then I'd love to hear ideas about how the index file hacking can be avoided - even just a way to #include index/contents files in a subdir without hacking the source paths for the html files to be relative to the top dir would be a big help. Regards, Dave. ---(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 This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the sender. This message contains confidential information and is intended only for the individual named. If you are not the named addressee you should not disseminate, distribute or copy this e-mail. ---(end of broadcast)--- TIP 4: Have you searched our list archives? http://archives.postgresql.org
[pgadmin-support] PgAdmin locked up
Hi All, I am really desperate for some help. PgAdmin is locked up on me. I had highlighted some text in a SQL window and when i mistakenly clicked on the highlighted text the cursor changed to something like a plus sign under an inverted L. sort of like this __ |+ Now I can't do anything! I really hate the idea of switching to a terminal and killing pgadmin. What is this and how can I get out? Kind Regards, Keith ---(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: [pgadmin-support] PgAdmin locked up
> -Original Message- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of > Keith Worthington > Sent: 16 June 2006 16:49 > To: pgadmin-support@postgresql.org > Subject: [pgadmin-support] PgAdmin locked up > > Hi All, > > I am really desperate for some help. PgAdmin is locked up on me. > > I had highlighted some text in a SQL window and when i > mistakenly clicked on the > highlighted text the cursor changed to something like a plus > sign under an > inverted L. sort of like this > __ > |+ > > Now I can't do anything! I really hate the idea of switching > to a terminal and > killing pgadmin. What is this and how can I get out? We've seen reports of this some versions of Ubuntu - see http://archives.postgresql.org/pgsql-general/2006-05/msg00897.php for a quick 'get-out'. It would appear to be a bug in the version of wxWidgets shipped with Ubuntu - see http://archives.postgresql.org/pgsql-general/2006-05/msg00900.php. Regards, Dave. ---(end of broadcast)--- TIP 3: Have you checked our extensive FAQ? http://www.postgresql.org/docs/faq
Re: [pgadmin-support] PgAdmin locked up
On Fri, 16 Jun 2006 16:56:42 +0100, Dave Page wrote > > -Original Message- > > From: [EMAIL PROTECTED] > > [mailto:[EMAIL PROTECTED] On Behalf Of > > Keith Worthington > > Sent: 16 June 2006 16:49 > > To: pgadmin-support@postgresql.org > > Subject: [pgadmin-support] PgAdmin locked up > > > > Hi All, > > > > I am really desperate for some help. PgAdmin is locked up on me. > > > > I had highlighted some text in a SQL window and when i > > mistakenly clicked on the > > highlighted text the cursor changed to something like a plus > > sign under an > > inverted L. sort of like this > > __ > > |+ > > > > Now I can't do anything! I really hate the idea of switching > > to a terminal and > > killing pgadmin. What is this and how can I get out? > > We've seen reports of this some versions of Ubuntu - see > http://archives.postgresql.org/pgsql-general/2006-05/msg00897.php for a > quick 'get-out'. It would appear to be a bug in the version of > wxWidgets shipped with Ubuntu - see > http://archives.postgresql.org/pgsql-general/2006-05/msg00900.php. > > Regards, Dave. Dave, Thanks for the info. Unfortunately I seem to be completely locked up. Is there a temp file somewhere that I can salvage my queries from? I have never looked before but I assume that when I kill pgadmin then my SQL will be gone. Is there a way to kill a specific SQL window and not all of pgadmin? Kind Regards, Keith ---(end of broadcast)--- TIP 4: Have you searched our list archives? http://archives.postgresql.org
Re: [pgadmin-support] PgAdmin locked up
> -Original Message- > From: Keith Worthington [mailto:[EMAIL PROTECTED] > Sent: 16 June 2006 17:09 > To: Dave Page; [EMAIL PROTECTED]; > pgadmin-support@postgresql.org > Subject: Re: [pgadmin-support] PgAdmin locked up > > Dave, > > Thanks for the info. Unfortunately I seem to be completely > locked up. Is there > a temp file somewhere that I can salvage my queries from? I > have never looked > before but I assume that when I kill pgadmin then my SQL will > be gone. Is there > a way to kill a specific SQL window and not all of pgadmin? Sorry, I'm afraid you're out of luck. Your only chance might be the pgAdmin or server logfiles if you've executed your queries and have statement logging turned on on either. Incidently - is this Ubuntu? Regards, Dave. ---(end of broadcast)--- TIP 5: don't forget to increase your free space map settings
Re: [pgadmin-support] PgAdmin locked up
On Fri, 16 Jun 2006 17:11:25 +0100, Dave Page wrote > > -Original Message- > > From: Keith Worthington [mailto:[EMAIL PROTECTED] > > Sent: 16 June 2006 17:09 > > To: Dave Page; [EMAIL PROTECTED]; > > pgadmin-support@postgresql.org > > Subject: Re: [pgadmin-support] PgAdmin locked up > > > > Dave, > > > > Thanks for the info. Unfortunately I seem to be completely > > locked up. Is there > > a temp file somewhere that I can salvage my queries from? I > > have never looked > > before but I assume that when I kill pgadmin then my SQL will > > be gone. Is there > > a way to kill a specific SQL window and not all of pgadmin? > > Sorry, I'm afraid you're out of luck. Your only chance might be the > pgAdmin or server logfiles if you've executed your queries and have > statement logging turned on on either. > > Incidently - is this Ubuntu? > > Regards, Dave. Dave, I do not know. I compiled it myself (with your help actually) the end of March. Here is what I can tell you. If you would like more then just ask. You might need to tell me where to look. ;-) If there is a way to fix this issue please let me know. I used to get bit by it regularly. That is why I went through the pain of compiling the latest pgadmin. I had thought until today that the bug was gone. Now with the fresh sting of a days worth of troubleshooting SQL lost I am off to save all my keystrokes. :-( pgAdmin3 1.4.2 wxGTK 2.6.2 Kind Regards, Keith ---(end of broadcast)--- TIP 2: Don't 'kill -9' the postmaster
Re: [pgadmin-support] Postgis Manual
Dave, We store all of our document souces in PhpWiki (though we could use any wiki that exports to XHTML). By creating a page that includes other wiki pages in the order we want them to appear in the help file, we create a single xhtml file that we convert to a docbook xml file and from there to html help. If you could find some way of putting all of your sources into one html file (we use the wiki include and transclude plugins) and following a similar path, you might find that merging HTML is easier than merging hhp projects. John -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Dave Page Sent: Friday, June 16, 2006 10:22 AM To: John Cole; Jeremy Palmer; pgadmin-support@postgresql.org Subject: Re: [pgadmin-support] Postgis Manual > -Original Message- > From: John Cole [mailto:[EMAIL PROTECTED] > Sent: 16 June 2006 16:11 > To: Dave Page; Jeremy Palmer; pgadmin-support@postgresql.org > Subject: RE: [pgadmin-support] Postgis Manual > > Dave, > How are you generating your help file? We use a xsl > stylesheet to convert > xhtml to docbook and from there generate the help project. > I'd be happy to > give you the stylesheet and our tool chain instructions. Hi John, The pgAdmin docs are maintained as HTML files, along with an HTML help project (hhp project file, hhk index file and hhc contents file). The PostgreSQL and Slony docs start out in SGML and are converted to individual HTML help projects using docbook & xsltproc. The difficult bit is merging them together. At the moment I manually merge the hhp, hhk and hhc files together, and adjust the paths as I go to allow for the fact that the slony and pg docs are in slony/ and pg/ directories relative to the pgadmin docs. Ideally, I'd like to be able to either automagically do the merge operation, or see if the files can be '#included' so that (for example) pgadmin.hhp includes something like: #include pg/postgresql.hhp #include slony/slony.hhp There is a way of doing that in HTMLHelp iirc, but it didn't like the fact the paths to the content files (*.html, *.gif etc) weren't relative to the top directory. I suspect the easiest answer is for a perl hacker to step forward and wave his or her wand, but I'm open to other suggestions :-) Regards, Dave. ---(end of broadcast)--- TIP 3: Have you checked our extensive FAQ? http://www.postgresql.org/docs/faq This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the sender. This message contains confidential information and is intended only for the individual named. If you are not the named addressee you should not disseminate, distribute or copy this e-mail. ---(end of broadcast)--- TIP 2: Don't 'kill -9' the postmaster
Re: [pgadmin-support] Postgis Manual
> -Original Message- > From: John Cole [mailto:[EMAIL PROTECTED] > Sent: 16 June 2006 19:04 > To: Dave Page; Jeremy Palmer; pgadmin-support@postgresql.org > Subject: RE: [pgadmin-support] Postgis Manual > > Dave, > We store all of our document souces in PhpWiki (though we > could use any > wiki that exports to XHTML). By creating a page that > includes other wiki > pages in the order we want them to appear in the help file, > we create a > single xhtml file that we convert to a docbook xml file and > from there to > html help. > > If you could find some way of putting all of your sources > into one html > file (we use the wiki include and transclude plugins) and following a > similar path, you might find that merging HTML is easier than > merging hhp > projects. We could do that with our docs, but not with the pg or slony ones - we have no choice but to pull them from the SGML sources whenever they are updated. Regards, Dave. ---(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: [pgadmin-support] PgAdmin locked up
> -Original Message- > From: Keith Worthington [mailto:[EMAIL PROTECTED] > Sent: 16 June 2006 17:29 > To: Dave Page; [EMAIL PROTECTED]; > pgadmin-support@postgresql.org > Subject: Re: [pgadmin-support] PgAdmin locked up > > > I do not know. I compiled it myself (with your help > actually) the end of March. Yes, but what OS are you running? Some linux distro? > Here is what I can tell you. If you would like more then > just ask. You might > need to tell me where to look. ;-) > > If there is a way to fix this issue please let me know. I > used to get bit by it > regularly. That is why I went through the pain of compiling > the latest pgadmin. > I had thought until today that the bug was gone. Now with > the fresh sting of a > days worth of troubleshooting SQL lost I am off to save all > my keystrokes. :-( > > pgAdmin3 1.4.2 > wxGTK 2.6.2 I'd definitely try a build against wx 2.6.3. And as with any program - save your work regularly!! Regards, Dave. ---(end of broadcast)--- TIP 4: Have you searched our list archives? http://archives.postgresql.org
Re: [pgadmin-support] PgAdmin locked up
On Fri, 16 Jun 2006 20:43:54 +0100, Dave Page wrote > > -Original Message- > > From: Keith Worthington [mailto:[EMAIL PROTECTED] > > Sent: 16 June 2006 17:29 > > To: Dave Page; [EMAIL PROTECTED]; > > pgadmin-support@postgresql.org > > Subject: Re: [pgadmin-support] PgAdmin locked up > > > > > > I do not know. I compiled it myself (with your help > > actually) the end of March. > > Yes, but what OS are you running? Some linux distro? > > > Here is what I can tell you. If you would like more then > > just ask. You might > > need to tell me where to look. ;-) > > > > If there is a way to fix this issue please let me know. I > > used to get bit by it > > regularly. That is why I went through the pain of compiling > > the latest pgadmin. > > I had thought until today that the bug was gone. Now with > > the fresh sting of a > > days worth of troubleshooting SQL lost I am off to save all > > my keystrokes. :-( > > > > pgAdmin3 1.4.2 > > wxGTK 2.6.2 > > I'd definitely try a build against wx 2.6.3. And as with any program - > save your work regularly!! > > Regards, Dave. Dave, I am running on RHEL3. I will try a new build next week. Yeah, ouch. The stuff I lost wasn't critical but it was two days worth of queries written while toubleshooting an anomoly. :-( Kind Regards, Keith Worthington President Narrow Path, Inc. 520 Trumbull Highway Lebanon, CT 06249-1424 Telephone: (860) 642-7114 Facsimile: (860) 237-8468 Mobile: (860) 608-6101 ---(end of broadcast)--- TIP 5: don't forget to increase your free space map settings
