Обсуждение: pgAdmin - no_spool
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi All, Could someone please tell me why when I click on a cluster pgAdmin exhibits a dialog stating: "Column not found in pgSet: no_spool" ? - - pgAdmin version 1.10.0 Beta2 rev. 7749 - - Master on a remote server - - Slony-I not installed on localhost TIA, - -- Pedro Doria Meunier GSM: +351 96 17 20 188 Skype: pdoriam -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org iD8DBQFKScxm2FH5GXCfxAsRArT8AJ0cOQok2fGxBjlZkgnY0DKMlUwivwCdHx89 u0d+m9gCvCQJMyo7Yo2hDX8= =vEzG -----END PGP SIGNATURE-----
On Tue, 2009-06-30 at 09:27 +0100, Pedro Doria Meunier wrote: > Could someone please tell me why when I click on a cluster pgAdmin > exhibits a dialog stating: > "Column not found in pgSet: no_spool" ? > > - - pgAdmin version 1.10.0 Beta2 rev. 7749 > - - Master on a remote server > - - Slony-I not installed on localhost > You need to ask this on the pgAdmin list. http://www.pgadmin.org/support/list.php -- Simon Riggs www.2ndQuadrant.com PostgreSQL Training, Services and Support
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Thanks Simon, Actually Dave has already made a patch that overcomes this issue and it's already been committed! BR, Pedro Doria Meunier GSM: +351 96 17 20 188 Skype: pdoriam Simon Riggs wrote: > On Tue, 2009-06-30 at 09:27 +0100, Pedro Doria Meunier wrote: > >> Could someone please tell me why when I click on a cluster >> pgAdmin exhibits a dialog stating: "Column not found in pgSet: >> no_spool" ? >> >> - - pgAdmin version 1.10.0 Beta2 rev. 7749 - - Master on a remote >> server - - Slony-I not installed on localhost >> > > You need to ask this on the pgAdmin list. > http://www.pgadmin.org/support/list.php > -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org iD8DBQFKTO6X2FH5GXCfxAsRAnKNAKCAo3XAieGNTXPoRpCh27Bnetm1GQCdE18M d0EjQ5jjuFBS0FX1kuWl3/g= =vNuh -----END PGP SIGNATURE-----
On Thu, 2009-07-02 at 18:30 +0100, Pedro Doria Meunier wrote: > Actually Dave has already made a patch that overcomes this issue and > it's already been committed! I replied to make sure that everybody knew where to post. If you post and then solve the problem its best to post again to say its solved and how it was solved. Otherwise google will not be our friend. -- Simon Riggs www.2ndQuadrant.com PostgreSQL Training, Services and Support