[pgadmin-support] Re: [pgadmin-support] Enc: Erro não identificado ao tentar efetuar o backup no PgAdmin 4

This is a bug & already reported https://redmine.postgresql.org/issues/1679 -- Regards, Murtuza Zabuawala EnterpriseDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company 2017-01-12 23:12 GMT+05:30 Info Optin.mobi : > Bom dia amigos, estou encontrando problemas ao efetuar backup e res

[pgadmin-support] Re: pgadmin4: enhancement request to remember column size rerunning a query

yes that would be fantastic :) -- View this message in context: http://postgresql.nabble.com/pgadmin4-enhancement-request-to-remember-column-size-rerunning-a-query-tp5930665p5937333.html Sent from the PostgreSQL - pgadmin support mailing list archive at Nabble.com. -- Sent via pgadmin-suppor

[pgadmin-support] Re: [pgadmin-support] 回复： [pgadmin-support] pgadmin4 command keep running and processwatcher won't go away

This is a bug, which was already been reported RM #1679 . I know - it's annoying to see that even though there is no process running in the background. If you can afford to loose the* server-list *from pgAdmin 4, you can delete the configuration file for

[pgadmin-support] Re: PgAdmin Debugger problem 56c2437d.4030...@enterprisedb.com (view raw or whole thread)

Hi Marc - sorry for the delay in replying to you. I'm working on replicating the problem. Will let you know if I have any difficulties (I'm working on setting up a Windows build environment with the proper versions now). -- Korry Korry, I could not find an entry point in t

Re: [pgadmin-support] Re: Bug#808924: pgadmin3 uses deprecated find -perm +xxx syntax, please switch to find -perm /+++

On Tue, Dec 29, 2015 at 6:01 PM, Christoph Berg wrote: > Control: tags -1 upstream > > Re: Andreas Metzler 2015-12-24 <20151224122927.gi1...@argenau.bebt.de> >> Hello, >> >> the pgadmin3 package uses find -perm +xxx. This GNU extension >> syntax is deprecated and does not work in GNU findutils 4.5

[pgadmin-support] Re: Bug#808924: pgadmin3 uses deprecated find -perm +xxx syntax, please switch to find -perm /+++

Control: tags -1 upstream Re: Andreas Metzler 2015-12-24 <20151224122927.gi1...@argenau.bebt.de> > Hello, > > the pgadmin3 package uses find -perm +xxx. This GNU extension > syntax is deprecated and does not work in GNU findutils 4.5.11 and > later. Please change to find -perm /xxx instead. > >

Re: [pgadmin-support] Re: PG admin 111 v 1.20 - autosuggestion , semantic check and query formatting Features

pgAdmin provides some basic functionality around autosuggestion and autocompletion but as you noticed, it's not as perfect as expected. I don't think pgAdmin is going to be improved in this area. I suggest to check other solutions. Personally I can recommend SQL Assistant we use in our company (

[pgadmin-support] Re: PG admin 111 v 1.20 - autosuggestion , semantic check and query formatting Features

Dear Team, We are using Postgre admin 111 version 1.20 with database server 9.3 enterprise edition for application development with a team size of 10 database developers.We are facing a high development efforts because of autosuggestion , semantic check and query formatting options are not a

[pgadmin-support] Re: [pgadmin-support] PGadmin 1.20.0 / Apple MBP 13 (early 2015) SwissGerman Keyboard [!¨][^`] keys bug

Hey Erwan, I'm facing a similar problem that, where I can't use the single quote ( ' ) character on my Brazilian Portuguese keyboard. Cheers On Mon, Jul 20, 2015 at 10:08 AM, Erwan Begoc wrote: > Hi All, > I could not find this bug listed anywhere. > > With PGadmin 1.20 from binary .dmg file,

[pgadmin-support] Re: Group role not shown in properties > Default Privileges after adding it

just ran into this same issue, there is something wrong with pgAdmin handling this in users eyes. like Aren, I want to create a role and grant privilege to a database. then only see 'public'. ok, find this post, it is intentional, then I go to "File > Options", there is no general tab. and I think

[pgadmin-support] Re[2]: [pgadmin-support] pgAgent build error,(Ubuntu)

tested, 100%, everything need is established, including  postgresql-server-dev-9.3 and libpq, otherwise "ccmake" will not configure sources. Четверг, 26 марта 2015, 8:30 +03:00 от Dmitry Voronin : >Make sure, that you install all postgresql packages >(postgresql-server-dev-9.3, and libpq). >

[pgadmin-support] Re[2]: [pgadmin-support] pgAgent build error,(Ubuntu)

tested, 100%, everything need is established, including  postgresql-server-dev-9.3 and libpq, otherwise "ccmake" will not configure sources. Четверг, 26 марта 2015, 8:29 +03:00 от Dmitry Voronin : >Make sure, that you install all postgresql packages >(postgresql-server-dev-9.3, and libpq).  > 

[pgadmin-support] Re[2]: [pgadmin-support] pgAgent build error,(Ubuntu)

tested, 100%, everything need is established, including  postgresql-server-dev-9.3 and libpq, otherwise "ccmake" will not configure sources. Четверг, 26 марта 2015, 8:30 +03:00 от Dmitry Voronin : >Make sure, that you install all postgresql packages >(postgresql-server-dev-9.3, and libpq). >

[pgadmin-support] Re[2]: [pgadmin-support] pgAgent build error

Thank you Dmitriy, but i already found where was my mistake)It exactly was missed libpq) Вторник, 24 марта 2015, 8:37 +03:00 от Воронин Дмитрий : >Beholder, hello. > >You must install libpq - dynamic client library for postgresql. And link it to >project. > >>  All steps for building doing l

Re: [pgadmin-support] Re: Unknown token in connection string

rg/docs/1.20/commandline.html > > regards, > Prasad > > > > Sent: Thursday, March 05, 2015 at 8:53 AM > From: "Dave Page" > To: Prasad > Cc: "pgAdmin Support" , Clodoaldo > > Subject: Re: [pgadmin-support] Re: Unknown token in connection strin

Re: [pgadmin-support] Re: Unknown token in connection string

age" To: Prasad Cc: "pgAdmin Support" , Clodoaldo Subject: Re: [pgadmin-support] Re: Unknown token in connection string On Wed, Mar 4, 2015 at 10:54 PM, Prasad wrote: > Looking at code, it looks like "connection string", is not expecting any > password and will p

Re: [pgadmin-support] Re: Unknown token in connection string

On Wed, Mar 4, 2015 at 10:54 PM, Prasad wrote: > Looking at code, it looks like "connection string", is not expecting any > password and will prompt for one. May well possibly a bug. No, it's a security "feature". Using passwords on the command line is a bad idea as other users can see it in ps

[pgadmin-support] Re: Unknown token in connection string

Looking at code, it looks like "connection string", is not expecting any password and will prompt for one. May well possibly a bug. regards, Prasad -- Sent via pgadmin-support mailing list (pgadmin-support@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref

[pgadmin-support] Re: [pgadmin-hackers] potential invalid input field of pgAdmin New Column GUI

Hi Sanket, On Fri, Nov 28, 2014 at 3:57 PM, Sanket Mehta wrote: > Hi Ashesh, > > On Wed, Nov 26, 2014 at 7:35 PM, Ashesh Vashi < > ashesh.va...@enterprisedb.com> wrote: > >> Hi Sanket, >> >> On Wed, Nov 26, 2014 at 5:41 PM, Akshay Joshi < >> akshay.jo...@enterprisedb.com> wrote: >> >>> Hi Sanket

[pgadmin-support] Re: [pgadmin-hackers] potential invalid input field of pgAdmin New Column GUI

Hi Ashesh, On Wed, Nov 26, 2014 at 7:35 PM, Ashesh Vashi wrote: > Hi Sanket, > > On Wed, Nov 26, 2014 at 5:41 PM, Akshay Joshi < > akshay.jo...@enterprisedb.com> wrote: > >> Hi Sanket >> >> Patch looks good to me. I have tested couple of scenarios and it works >> fine. >> >> On Wed, Nov 26, 2014

[pgadmin-support] Re: [pgadmin-hackers] potential invalid input field of pgAdmin New Column GUI

Hi Sanket, On Wed, Nov 26, 2014 at 5:41 PM, Akshay Joshi wrote: > Hi Sanket > > Patch looks good to me. I have tested couple of scenarios and it works > fine. > > On Wed, Nov 26, 2014 at 3:27 PM, Sanket Mehta < > sanket.me...@enterprisedb.com> wrote: > >> Hi Akshay, >> >> >> On Tue, Nov 25, 2014

[pgadmin-support] Re: [pgadmin-hackers] potential invalid input field of pgAdmin New Column GUI

Hi Sanket Patch looks good to me. I have tested couple of scenarios and it works fine. On Wed, Nov 26, 2014 at 3:27 PM, Sanket Mehta wrote: > Hi Akshay, > > > On Tue, Nov 25, 2014 at 2:57 PM, Akshay Joshi < > akshay.jo...@enterprisedb.com> wrote: > >> Hi Sanket >> >> On Mon, Nov 24, 2014 at 5:1

[pgadmin-support] Re: [pgadmin-hackers] potential invalid input field of pgAdmin New Column GUI

Hi Akshay, On Tue, Nov 25, 2014 at 2:57 PM, Akshay Joshi wrote: > Hi Sanket > > On Mon, Nov 24, 2014 at 5:18 PM, Sanket Mehta < > sanket.me...@enterprisedb.com> wrote: > >> Hi Akshay, >> >> >> On Wed, Nov 19, 2014 at 4:39 PM, Akshay Joshi < >> akshay.jo...@enterprisedb.com> wrote: >> >>> Hi San

[pgadmin-support] Re: [pgadmin-hackers] potential invalid input field of pgAdmin New Column GUI

Hi Sanket On Mon, Nov 24, 2014 at 5:18 PM, Sanket Mehta wrote: > Hi Akshay, > > > On Wed, Nov 19, 2014 at 4:39 PM, Akshay Joshi < > akshay.jo...@enterprisedb.com> wrote: > >> Hi Sanket >> >> Below are the file wise review comments >> >> >>1. ctlSeclabelPanel.cpp and ctlSeclabelPanel.h >>

[pgadmin-support] Re: [pgadmin-hackers] potential invalid input field of pgAdmin New Column GUI

Hi Akshay, On Wed, Nov 19, 2014 at 4:39 PM, Akshay Joshi wrote: > Hi Sanket > > Below are the file wise review comments > > >1. ctlSeclabelPanel.cpp and ctlSeclabelPanel.h >- Correct the function name "GetCUrrentProviderLabelArray" according > to camel case. > - Use trim bef

[pgadmin-support] Re: [pgadmin-hackers] potential invalid input field of pgAdmin New Column GUI

Hi Sanket Below are the file wise review comments 1. ctlSeclabelPanel.cpp and ctlSeclabelPanel.h - Correct the function name "GetCUrrentProviderLabelArray" according to camel case. - Use trim before check the empty condition of txtProvider and txtSeclabel used in ctlSecla

[pgadmin-support] Re: [pgadmin-hackers] potential invalid input field of pgAdmin New Column GUI

Hi Akshay, PFA the patch. Please review it and let me know if anything is missing. Regards, Sanket Mehta Sr Software engineer Enterprisedb On Tue, Nov 11, 2014 at 7:21 PM, Ashesh Vashi wrote: > Hi Sanket, > > Apart from variable persistence issue taken care in your patch, I've also > observed

[pgadmin-support] Re: [pgadmin-hackers] potential invalid input field of pgAdmin New Column GUI

Hi, Below are the thing I have taken care in this patch: 1. While creating the new table using table wizard, when any variables or security labels are specified for certain column, those were not visible on *sql tab* of table wizard. 2. when new/existing column dialog is open from table dialog th

[pgadmin-support] Re: [pgadmin-hackers] potential invalid input field of pgAdmin New Column GUI

Hi Sanket, Apart from variable persistence issue taken care in your patch, I've also observed the data persistence issue with: (When reloading the existing/new column in column dialog from table dialog) 1. Priviledges 2. Security Lables I also observed, when I remove some privileges from an exist

[pgadmin-support] Re: [pgadmin-hackers] potential invalid input field of pgAdmin New Column GUI

Hi Sanket, Quick review suggests that, you're not following the consistent name convention in new functions as per pgAdmin3 coding standard. I also observed a white-space warning, while apply the patch. Please resend the patch after resolving these issues. -- Thanks & Regards, Ashesh Vashi Ent

[pgadmin-support] Re: [pgadmin-hackers] potential invalid input field of pgAdmin New Column GUI

Hi, Issue was occurring as mentioned below: While creating the new table using table wizard, when any variables or security labels are specified for certain column then in *dlgTable* class, it was not fetching those variable or security labels from *dlgColumn *class. So those were not visible on

[pgadmin-support] Re: [pgadmin-hackers] potential invalid input field of pgAdmin New Column GUI

Sure Ashesh, I will check and get back. Regards, Sanket Mehta Sr Software engineer Enterprisedb On Tue, Nov 4, 2014 at 1:03 PM, Ashesh Vashi wrote: > Sanket, > > Can you take a look at it? > > -- > Thanks, > > Ashesh Vashi > > On 4 Nov 2014 12:54, "liuyuanyuan" wrote: > > > > > > > > Hi , ha

[pgadmin-support] Re: [pgadmin-hackers] potential invalid input field of pgAdmin New Column GUI

Sanket, Can you take a look at it? -- Thanks, Ashesh Vashi On 4 Nov 2014 12:54, "liuyuanyuan" wrote: > > > > Hi , hackers! > > Currently I test some part of pgadmin GUI, and I found some potential invalid input field of New Column GUI, > > Like Variables and Security Labels. Could you please ha

Re: [pgadmin-support] Re: BUG REPORT: SQL Editor selects too much text after you hit return and select "one line"

On Mon, Jun 23, 2014 at 1:50 PM, k mac wrote: > My MacBook Air runs OS X 10.8.5 and pgAdmin III was packaged by EnterpriseDB > and downloaded from > > http://www.enterprisedb.com/products-services-training/pgdownload > > Is is possible that this version of pgAdmin is configured differently than >

Re: [pgadmin-support] Re: BUG REPORT: SQL Editor selects too much text after you hit return and select "one line"

My MacBook Air runs OS X 10.8.5 and pgAdmin III was packaged by EnterpriseDB and downloaded from http://www.enterprisedb.com/products-services-training/pgdownload Is is possible that this version of pgAdmin is configured differently than yours? On Fri, Jun 20, 2014 at 11:23 AM, Dave Page wrote

Re: [pgadmin-support] Re: BUG REPORT: SQL Editor selects too much text after you hit return and select "one line"

On Wed, Jun 18, 2014 at 1:37 AM, k mac wrote: > Dmitriy, > > When I disabled "Auto Indent" the issue went away. Thank you and good job! > I've tested both with and without auto indent, and can't reproduce the problem on my mac :-/ > > Note: "Auto indent" was already enabled when I installed Po

Re: [pgadmin-support] Re: BUG REPORT: SQL Editor selects too much text after you hit return and select "one line"

Dmitriy, When I disabled "Auto Indent" the issue went away. Thank you and good job! Note: "Auto indent" was already enabled when I installed PostgreSQL. Shouldn't the default be to have "Auto indent" disabled ? Thanks again. On Tue, Jun 17, 2014 at 7:18 PM, Dmitriy Olshevskiy wrote: > Hi.

Re: [pgadmin-support] Re: BUG REPORT: SQL Editor selects too much text after you hit return and select "one line"

Hi. You have enabled "Auto indent" mode (menu Edit in query tool window)? I found that in case when this mode is disabled and there are no indents in sql editor, everything seems to be alright. 17.06.2014 21:14, k mac пишет: Hello, I received one response to my enquiry asking me to "Change yo

Re: [pgadmin-support] Re: BUG REPORT: SQL Editor selects too much text after you hit return and select "one line"

> If your OS is using the default US keyboard mapping layout yes, it is. > then this probably is not the issue, Unfortunately, I wish it was. I use the EnterpriseDB installer from http://www.enterprisedb.com/products-services-training/pgdownload to install on a Macbook Air with US English k

Re: [pgadmin-support] Re: BUG REPORT: SQL Editor selects too much text after you hit return and select "one line"

On Tue, 2014-06-17 at 13:14 -0400, k mac wrote: > Hello, > > > I received one response to my enquiry asking me to "Change your > keyboard" which is something I cannot do, as the keyboard is part of > the notebook I'm typing on. > > > > Not sure of the process here. Should I expect a response f

Re: [pgadmin-support] Re: BUG REPORT: SQL Editor selects too much text after you hit return and select "one line"

Hi On Tue, Jun 17, 2014 at 6:14 PM, k mac wrote: > Hello, > > I received one response to my enquiry asking me to "Change your keyboard" > which is something I cannot do, as the keyboard is part of the notebook I'm > typing on. > > Not sure of the process here. Should I expect a response from su

[pgadmin-support] Re: BUG REPORT: SQL Editor selects too much text after you hit return and select "one line"

Hello, I received one response to my enquiry asking me to "Change your keyboard" which is something I cannot do, as the keyboard is part of the notebook I'm typing on. Not sure of the process here. Should I expect a response from support or development? If so, within a week, month, … ? Thanks O

Re: [pgadmin-support] Re: PGAdmin for PostgreSQL 9.3 creates tables with double quotes embedded in the name

On Mon, Jun 2, 2014 at 7:09 PM, David G Johnston wrote: >> >> I >> f all the letters are lowercase, no double quotes are added. > > > I don't know if this statement is actually true but it makes no difference > in reality whether the double-quotes are added in the case where only > lowercase lette

[pgadmin-support] Re: PGAdmin for PostgreSQL 9.3 creates tables with double quotes embedded in the name

> > > ​I​ > f all the letters are lowercase, no double quotes are added. > ​I don't know if this statement is actually true but it makes no difference in reality whether the double-quotes are added in the case where only lowercase letters and numbers/underscore are used. As far the executor is co

[pgadmin-support] Re: [pgadmin-support] pgAdmin 1.18.1 (win7) shows dots

Hi, Konstantin! Try to check out this config option: File > Options... > Query Editor > Max. characters per column. Perhaps now the value is "0". In this case, set the value greater than 0. # Dmitriy Olshevskiy Sun, 1 Jun 2014 13:30:05 +0300 от Konstantin Mikhailov : >Using query window input

[pgadmin-support] Re: PGAdmin for PostgreSQL 9.3 creates tables with double quotes embedded in the name

RobR wrote > I then concluded that the table was being created with the double quotes > included in the table name. In short: log = "log" Log = "log" Log = log LoG = lOg Log <> "Log" Again, this is all just parser stuff. Whatever is present post-parse on a create table is stored, as-is, in the

[pgadmin-support] Re: PGAdmin for PostgreSQL 9.3 creates tables with double quotes embedded in the name

RobR wrote > I selected the database in PGAdmin, went down to the Tables list (which > said I had 0 table), right clicked on the word "Tables", and selected "New > table". In the new table dialog I entered the table name as Log (no > quotes) Enter the table name in lower-case. If you cannot surr

[pgadmin-support] Re: Use of uninitialized value $info{"pgdata"} in concatenation (.) or string at /usr/bin/pg_ctlcluster

espeake wrote > at /usr/bin/pg_ctlcluster This is a Debian/Ubuntu supplied script; not PostgreSQL core. The main packaging site is located here: http://wiki.postgresql.org/wiki/Apt and includes contact links/references. David J. -- View this message in context: http://postgresql.1045698.

Re: [pgadmin-support] RE: [pgadmin-support] will 1.18.0 be available for download from the www.pgadmin.org site?

rds, > > peter > > > > > > > > From: pgadmin-support-ow...@postgresql.org > [mailto:pgadmin-support-ow...@postgresql.org] On Behalf Of Dan Halbert > Sent: Tuesday, September 10, 2013 2:08 PM > To: pgadmin-support@postgresql.org > Subject: [pgadmin-support] RE: [

[pgadmin-support] RE: [pgadmin-support] will 1.18.0 be available for download from the www.pgadmin.org site?

On Tuesday, September 10, 2013 2:55pm, "Belbin, Peter" said: > I appreciate that pgAdmin 1.18.0 is available for windows users as part of the > EnterpriseDB bundle, but, for those of us that really don't want/need the > postgresql db running locally, will 1.18.0 be available for download from

Re: [pgadmin-support] RE: [pgadmin-support] will 1.18.0 be available for download from the www.pgadmin.org site?

t Sent: Tuesday, September 10, 2013 2:08 PM To: pgadmin-support@postgresql.org Subject: [pgadmin-support] RE: [pgadmin-support] will 1.18.0 be available for download from the www.pgadmin.org site? On Tuesday, September 10, 2013 2:55pm, "Belbin, Peter" mailto:peter.bel...@windstream.com>>

[pgadmin-support] Re: Second message: "Problem generating database using pgAdmin III - PostgreSQL version is 9.1"

Hi Paul. Your question is undoubtedly beyond the scope of this forum, which would explain the mute response. I can't say for certain I know what you are trying to accomplish but I think I have a pretty good idea. I would be happy to try and assist you but I recommend that we take our conversa

Re: [pgadmin-support] Re: cannot remove some items from the server list after upgrade from postgres 8.x to 9.x

On Tue, Apr 30, 2013 at 7:36 AM, Gary Oberholster wrote: > > I am having this problem as well when upgrading from 8.3 to 9.2 using the > dump, uninstall, install and restore procedure. > > I have found that whenever you use pgAdmin III, it writes it's current state > to the registry under HKEY_USE

[pgadmin-support] Re: cannot remove some items from the server list after upgrade from postgres 8.x to 9.x

Dave Page-7 wrote > On Mon, Jan 10, 2011 at 1:29 PM, Doug Easterbrook < > doug@ > > wrote: >> we do. >> >> on windows, standard procedure on an upgrade is to: >> a) dump the database >> b) go to add/remove programs and remove the old server (it leaves the >> database 'data' around) >> c) install

[pgadmin-support] Re: compiling on debian does not find a valid PostgreSQL 8.4+ installati

thanks Guillaume, after installing postgresql-server-dev-8.4 libwxgtk2.8-0 libwxgtk2.8-dev libxml2-dev libxslt-dev I just ran ./configure and I got to intall pgAdmin III 1.8.4thanks again! -- View this message in context: http://postgresql.1045698.n5.nabble.com/compiling-on-debian-does-not-find

Re: [pgadmin-support] Re: Possible bug report (comment on database disappered on pgAdmin 1.16.1)

On Wed, Feb 6, 2013 at 2:03 PM, Vjacheslav A. wrote: > The same issue is for me, comments just not displayed in 1.16.1, > but normally displayed in 1.14.3, > WinXP SP3, PG 9.1.7. > > > > On Wed, Feb 6, 2013 at 4:56 PM, ldrlj1 wrote: >> >> how to recreate issue: >> Right click on database name >>

Re: [pgadmin-support] Re: Possible bug report (comment on database disappered on pgAdmin 1.16.1)

The same issue is for me, comments just not displayed in 1.16.1, but normally displayed in 1.14.3, WinXP SP3, PG 9.1.7. On Wed, Feb 6, 2013 at 4:56 PM, ldrlj1 wrote: > how to recreate issue: > Right click on database name > Choose Properties > Enter some text in the comments area > Click OK. >

[pgadmin-support] Re: Possible bug report (comment on database disappered on pgAdmin 1.16.1)

how to recreate issue: Right click on database name Choose Properties Enter some text in the comments area Click OK. When you open up the properties for the database, you will not see the comments previously entered. Those comments are stored in pg_shdescription. -- View this message in context

Re: [pgadmin-support] Re: Group role not shown in properties > Default Privileges after adding it

On Mon, 2012-05-28 at 09:55 -0500, Aren Cambre wrote: > > This doesn't make sense. If I create a login role, it should show up here > >> and allow me to assign it to arbitrary tables. > >> > > > > That's intentional (and configurable): see > > http://www.pgadmin.org/support/faq.php#UserPrivileges >

Re: [pgadmin-support] Re: Group role not shown in properties > Default Privileges after adding it

> This doesn't make sense. If I create a login role, it should show up here >> and allow me to assign it to arbitrary tables. >> > > That's intentional (and configurable): see > http://www.pgadmin.org/support/faq.php#UserPrivileges > Argh, thanks. Now I remember running into this before. This nee

Re: [pgadmin-support] Re: Group role not shown in properties > Default Privileges after adding it

On Mon, May 28, 2012 at 10:39 AM, Aren Cambre wrote: > Looks like pgAdmin's user handling is broken or nonsensical. Just as a > test, I created a new login role named *test*. Here's its SQL: > *CREATE ROLE test LOGIN* > * ENCRYPTED PASSWORD 'md505a671c66aefea124cc08b76ea6d30bb'* > * NOSUPERUSER

[pgadmin-support] Re: Bug: Constraint Trigger - created with pgadmin - is not visible and missing in SQL Pane / Create Script

Did some research on system catalogs and how to retrieve constraint triggers: Internal triggers (addressed in "CREATE CONSTRAINT TRIGGER in SQL pane (pgAdmin 1.14.1)" from Thu, 15 Dec 2011 15:39:37 +0200 ) have tgisinternal set to true in table pg_trigger. Constraint triggers (I was talking ab

Re: [pgadmin-support] Re: [pgadmin-hackers] PGADMIN3 request for preferences-related behavior change

On Sun, Mar 25, 2012 at 9:06 AM, Guillaume Lelarge wrote: > On Sat, 2012-03-24 at 12:05 -0400, John Genoese wrote: > > We think alike, my friend. The only thing is that I need two scripts: > > one to copy and start the app, and a second one after the app closes > > to copy back any config updates.

[pgadmin-support] Re: [pgadmin-hackers] PGADMIN3 request for preferences-related behavior change

On Sat, 2012-03-24 at 12:05 -0400, John Genoese wrote: > We think alike, my friend. The only thing is that I need two scripts: > one to copy and start the app, and a second one after the app closes > to copy back any config updates. > > > As you most likely already know, on the Mac there is one

[pgadmin-support] RE : demande de doc

Bonjour, la documentation est disponible ici : http://www.pgadmin.org/docs/ Seulement en anglais. Hi, The documentation is available here : http://www.pgadmin.org/docs/ Florence Cousin.

[pgadmin-support] RE : demande de doc

Bonjour, la documentation est disponible ici : http://www.pgadmin.org/docs/ Seulement en anglais. Hi, The documentation of pgAdmin is available here : http://www.pgadmin.org/docs/ Florence Cousin. De : pgadmin-support-ow...@postgresql.org [pgadmin-support-ow...@postgresql.

Re: [pgadmin-support] Re: Bug - Rows in Query Output pane fail to grow in height when font size preference size is larger

On Wed, 2011-10-26 at 18:02 -0700, Josh Berkus wrote: > > It also happens on Linux. Now fixed. Thanks :) > > Is there somewhere I could download a snapshot for OSX? Nope. If you asked for a Linux or Windows snapshot, I could probably build one. But Mac OS X, I can only compile a debug version of

Re: [pgadmin-support] Re: Bug - Rows in Query Output pane fail to grow in height when font size preference size is larger

> It also happens on Linux. Now fixed. Thanks :) Is there somewhere I could download a snapshot for OSX? I have some demos later this month and would love to be able to enlarge the text a bit. -- Josh Berkus PostgreSQL Experts Inc. http://pgexperts.com -- Sent via pgadmin-support mailing lis

Re: [pgadmin-support] Re: Bug - Rows in Query Output pane fail to grow in height when font size preference size is larger

On Wed, 2011-10-12 at 23:17 -0700, Basil Bourque wrote: > >> The bug is that the size of the row (height) does NOT react to the point > >> size specified in Preferences. > > > > I think what Guillaume meant is the main Font selection at the top of the > > Preferences tab which affects all the font

Re: [pgadmin-support] Re: Bug - Rows in Query Output pane fail to grow in height when font size preference size is larger

>> The bug is that the size of the row (height) does NOT react to the point >> size specified in Preferences. > > I think what Guillaume meant is the main Font selection at the top of the > Preferences tab which affects all the font in pgAdmin III. You changed the > Font in the Query Tool tab. >

[pgadmin-support] Re: After upgrade from 8.3 to 8.4 in OS X the same server is appearing twice

Dave Thanks Dave that is exactly what has happened, I forgot I had installed the previous version from EDB. All fixed now Peter On 8 Jul 2011, at 18:11, Dave Page-7 [via PostgreSQL] wrote: > On Fri, Jul 8, 2011 at 4:45 PM, Peter Hickman <[hidden email]> wrote: > > I recently upgraded my postg

[pgadmin-support] Re: Bug - Rows in Query Output pane fail to grow in height when font size preference size is larger

Basil Bourque-2 wrote: > > The bug is that the size of the row (height) does NOT react to the point > size specified in Preferences. > I think what Guillaume meant is the main Font selection at the top of the Preferences tab which affects all the font in pgAdmin III. You changed the Font in the

[pgadmin-support] Re: PgAdmin III hangs When SQL button clicked or when opening a script from a database object

Hi All, I found the solution for this bug. By just deleting the postgresql folder in Application Data folder this will solve. Thanks and Regards Amila Jayasooriya On Fri, Feb 18, 2011 at 12:45 PM, Amila Jayasooriya < amilajayasoor...@gmail.com> wrote: > Hi All, > > This is the second time

[pgadmin-support] Re: Query Tool history makes the Query Tool unusable after BIG query had been executed

On my machine I also do not see any problems on the modern machine, the problem was to be seen on the older notebook. Sorry for not noticing the limit on the query size... strange, that though the limit is there by default, a humongous query lead to the hangup of the query tool on the older notebo

[pgadmin-support] Re: [GENERAL] MS Access 2007 update write conflict problem & resolution

On Fri, Mar 19, 2010 at 11:12 AM, jus...@magwerks.com wrote: > > The bigger problem is using time stamps to find the record for updating > > Timestamps will not be unique as more than 1 record can have the same value > > I suggest changing the updating method to use a unique key. MS-Access achiev

Re: [pgadmin-support] Re: PgAdmin browses all tables, even those not allowed

I don't think the assumption that CREATE implies SELECT is a good one. It is probably true in most cases, but there might be folks that have set it up otherwise. It seems that the Dependents tab on a role under the Login Roles might be the place to look for tables, etc, that the login has access t

Re: [pgadmin-support] Re: PgAdmin browses all tables, even those not allowed

When I say end-user I am thinking from a Data Warehouse perspective where there are many SELECT-only users. For them, their experience is frustrating and confusing when they need to go through many schemas and tables that they don't care about to find what they can access. That is why I sugge

[pgadmin-support] Re: PgAdmin browses all tables, even those not allowed

Thank for your answer. There are advantages / disavantages for end-users with the 2 solutions Solution 1: Let the end-user see only the schemas/tables he is allowed to use (as Oracle SQL Developper does, for example) : + : easy to retrieve their data without been lost if the database has

Re: [pgadmin-support] Re: Graphical Query Builder enable/disable switch (or confirmation dialog)

On Wed, Apr 8, 2009 at 2:16 PM, valgog wrote: > Actually the request about the slowness of the switching between > databases in Query window is much, much more important in our case (as > we switch from standby and live databases quite often having one file > open in the Query window). I can imag

[pgadmin-support] Re: Graphical Query Builder enable/disable switch (or confirmation dialog)

On Apr 8, 3:01 pm, dp...@pgadmin.org (Dave Page) wrote: > On Wed, Apr 8, 2009 at 1:38 PM, valgog wrote: > > Hi, > > > When you accidentally click on the scary tab (I managed to do it twice > > already) the whole pgAdmin is blocked for more then 3 minutes. It is > > not normal not to ask for a conf

Re: [pgadmin-support] Re: Graphical Query Builder enable/disable switch (or confirmation dialog)

On Wed, Apr 8, 2009 at 1:38 PM, valgog wrote: > Hi, > > When you accidentally click on the scary tab (I managed to do it twice > already) the whole pgAdmin is blocked for more then 3 minutes. It is > not normal not to ask for a confirmation before some long lasting > operation (especially when the

[pgadmin-support] Re: Graphical Query Builder enable/disable switch (or confirmation dialog)

Hi, When you accidentally click on the scary tab (I managed to do it twice already) the whole pgAdmin is blocked for more then 3 minutes. It is not normal not to ask for a confirmation before some long lasting operation (especially when the button to start this operation locates directly under mos

[pgadmin-support] Re : Re : Problem in connecting pgagent service to the database server

I found the mistake i put host    all all 0.0.0.1/0  trust That would accept any connection - Message d'origine De : houssem jemel <[EMAIL PROTECTED]> À : pgadmin-support@postgresql.org Envoyé le : Jeudi, 4 Décembre 2008, 16h12mn 45s Objet : Re : Problem in conne

[pgadmin-support] Re : Problem in connecting pgagent service to the database server

That may help you to diagnostic the problem: I open the pgadmin in the distant machine 192.168.1.2, and tried to connect to the database server I got this error : Error connecting to the server: FATAL , no entry in pg_hba.conf for host 192.168.1.2 Althoug i put in the pg_hba.conf host    all  

[pgadmin-support] Re: [Fwd: Re: sudden program termination: no warning, error, or crash]

On Sep 26, 12:34 pm, [EMAIL PROTECTED] (Erwin Brandstetter) wrote: > Hi Kev! > > Please send this to the list, not to my private email account: > > [EMAIL PROTECTED] > > Regards > Erwin Oh, no wonder...after a certain amount of time, there isn't actually a "reply" option on Google Group thread

[pgadmin-support] Re: Instalación

Hello, I want to learn postgresql in pgAdmin 3 but not as install windons desire to know how this is HEC ; thanks before hand.!

[pgadmin-support] Re: [pgadmin-support] cours administr ation et de développement pgadmin III

Idrissa Dera a écrit : J'utilisais une base de années accès depuis plus de deux ans en tant administrateur. Hier, la base de données a été migré en PostgreSQL. Je viens par ce mail vous solliciter des cours ou tutoriel d'administration et de développement pgadmin III. Ceci une liste de di

[pgadmin-support] Re: [BUGS] BUG #3829: Wrong index reporting from pgAdmin III (v1.8.0 rev 6766-6767)

Added to TODO: * Add a function like pg_get_indexdef() that report more detailed index information http://archives.postgresql.org/pgsql-bugs/2007-12/msg00166.php --- Dave Page wrote: > Tom Lane wrote: > >> We use the

Re : [pgadmin-support] Re : Reporting ?

] The Computing Froggy - Message d'origine De : Guillaume Lelarge <[EMAIL PROTECTED]> À : Laurent ROCHE <[EMAIL PROTECTED]> Cc : pgadmin-support@postgresql.org Envoyé le : Vendredi, 25 Janvier 2008, 10h31mn 18s Objet : Re: [pgadmin-support] Re : Reporting ? Laurent ROCHE w

Re : [pgadmin-support] Re : Reporting ?

Hi Dave, I understand you have plenty of things to do as it is. But may be being able to generate a report on many objects instead of only one would not be such a big work. Anyway autodoc does a good job at generating report. Cheers, [EMAIL PROTECTED] The Computing Froggy - Message d'or

Re: [pgadmin-support] Re : Reporting ?

Laurent ROCHE wrote: So nobody is doing any reporting on the PG tables with pgAdmin ... or even something else ? postgresql-autodoc is an easy tool to use with many output formats. See http://www.rbt.ca/autodoc/ for details. -- Guillaume. http://www.postgresqlfr.org http://dalibo.com -

Re: [pgadmin-support] Re : Reporting ?

> - Message d'origine > De : Laurent ROCHE <[EMAIL PROTECTED]> > À : pgadmin-support@postgresql.org > Envoyé le : Mercredi, 23 Janvier 2008, 17h49mn 30s > Objet : Reporting ? > > > > Hi, > > > I am trying to generate reports for my database. > > I have never used this before so I might be

[pgadmin-support] Re : Reporting ?

Hi, So nobody is doing any reporting on the PG tables with pgAdmin ... or even something else ? Cheers, [EMAIL PROTECTED] The Computing Froggy - Message d'origine De : Laurent ROCHE <[EMAIL PROTECTED]> À : pgadmin-support@postgresql.org Envoyé le : Mercredi, 23 Janvier 2008, 17h49mn

[pgadmin-support] Re : [pgadmin-support] Información pgAdmin

Hola Ángela, Esto es una mailing list en Ingles solo. This is a mailing list in English only. La mailing list en Castellano es pgsql-es-ayuda ! Aqui esta la documentacion para PostgreSQL http://www.postgresql.org/docs/ click a la derecha en la version que utilizas Pero la documentacion para pgA

[pgadmin-support] Re: [BUGS] BUG #3829: Wrong index reporting from pgAdmin III (v1.8.0 rev 6766-6767)

Tom Lane wrote: We use the data in various UI elements as well as for reverse engineering the SQL - it's easier to get it broken down than to parse it back out of the complete definition. Seems like all the more argument for having functions that extract single pieces of information, rather tha

[pgadmin-support] Re: [BUGS] BUG #3829: Wrong index reporting from pgAdmin III (v1.8.0 rev 6766-6767)

Tom Lane wrote: > I dug through the archives and found that we've had this discussion > before ;-). The basic argument for having the per-column form of > pg_get_indexdef do what it does was that it's unreasonable for > client-side code to try to disassemble an expression tree string, > whereas ex

[pgadmin-support] Re: [BUGS] BUG #3829: Wrong index reporting from pgAdmin III (v1.8.0 rev 6766-6767)

Tom Lane wrote: > NikhilS <[EMAIL PROTECTED]> writes: >>> Looks like pg_get_indexdef is unwell :-( > >> yes, it was unwell in the area where the amcanorder was being processed. The >> attached patch should fix this. > > Hm, there is a definitional issue here. Should pg_get_indexdef print > this

[pgadmin-support] Re: [BUGS] BUG #3829: Wrong index reporting from pgAdmin III (v1.8.0 rev 6766-6767)

Pavel Stehule wrote: > Hello > > it's pgAdmin bug. please report it there Actually it doesn't appear to be... Using the OPs example code on 8.3 beta 4: >> CREATE INDEX test_desc_idx1 >> ON test_desc >> USING btree >> (f1, f2 desc) >> >> CREATE INDEX test_desc_idx2 >> ON test_desc >> U

[pgadmin-support] Re: pgAdmin windows installer: Need a "file extension association" option

LiuYan 刘研 написа: > Can pgAdmin windows installer give user a "file extension association" > option, so that I can keep using my original/favorite text editor to > open/edit .sql files? [...] You may find this old thread informative - http://www.pgadmin.org/archives/pgadmin-hackers/2007-05/msg001

[pgadmin-support] Re: [PORTS] pgadmin3 on Fedora7 - can't run standard binary, can't compile from source..

Strange, grabbing the spacer bar definitely does not work for me. The cursor remains looking like an arrow as I pass over the spacer bars, with the exception that it changes to an I beam in the SQL pane. --- The compile bug I fixed was probably due to differences in gcc compiler versions. I a

  1   2   >