Re: [pgadmin-support] On 19010 pgAdmin doesn't run

[Andy Shellam]

I would like more to why your computer shows 19010 as the year, as 
that's a completely invalid date.  I don't think Windows currently 
handles years after 2099.


I don't know what the developers think, but I think this is a problem 
outside of the developer's control.


Andy.

Ezequias Rodrigues da Rocha wrote:

Hi list,

My computer is with a baterry problem and sometimes the Year of 
Windows shows 19010.


On this date PgAdmin doesn't run. I don't know if you already noticed 
it but you could try.


Regards ...

--
Ezequias Rodrigues da Rocha
http://ezequiasrocha.blogspot.com/
use Mozilla Firefox:http://br.mozdev.org/firefox/ 
 !DSPAM:37,45f400a4103001014560638! 



---(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

[pgadmin-support] Default "maximum rows to retrieve" setting

[Andy Shellam]

Hi,

In the Preferences options, there's an option on the Query tab that says 
"Maximum rows to retrieve."  This is currently set to 100, but I can't 
see how/where it takes effect.


I have a table that's growing an average of 250 rows a day (currently at 
1098 rows.)  If I select the table, and use the toolbar button "view 
data in selected object", it retrieves all rows, with the limit 
drop-down set to "No Limit."


If I open the query editor, and type "SELECT * FROM large_table;" that 
retrieves all rows as well.  I have to manually key "LIMIT 1000" in the 
query, or change the drop-down in the view data dialogue (after all data 
has been downloaded.)


Ideally what I'd like is to set the default rows to retrieve to 1000, so 
it downloads the first 1000 rows when I open the table, and then I can 
choose to retrieve others if I need to.


Thanks

Andy.

---(end of broadcast)---
TIP 4: Have you searched our list archives?

  http://archives.postgresql.org

Re: [pgadmin-support] Default "maximum rows to retrieve" setting

[Andy Shellam]

Dave Page wrote:



Ideally what I'd like is to set the default rows to retrieve to 1000, so
it downloads the first 1000 rows when I open the table, and then I can
choose to retrieve others if I need to.



I'd love to!  But I'm afraid I don't know C/C++ programming, and have 
never done anything with WxWidgets.


If someone else wants to have a go, I could see perhaps having a text 
box within the "View data (filtered)" dialogue that would take the 
default setting of "max. rows to retrieve" but give you the option to 
override it to 0 (unlimited) or some other figure, and that would apply 
the "LIMIT" clause to the query, just as it does the "WHERE" clause 
currently.


So it would end up that "View all" does the same as it does now, but 
"View data (filtered)" gives you both the WHERE filter and the LIMIT clause.


Hope this helps someone!

Andy.

---(end of broadcast)---
TIP 2: Don't 'kill -9' the postmaster

Re: [pgadmin-support] No backup/restore for Linux?

[Andy Shellam]

Hi Mark,

Are the options there, just disabled?  Or not there at all?
You say you're missing the "table backup/restore" - you mean when you 
right-click on a table?  Are the options there at the database level?


IIRC I had it where the backup/restore were disabled in Fedora Core 5, 
and it was because PgAdmin couldn't use the pg_dump and pg_restore 
exec's in the PgAdmin directory.  Failing that, I don't know any further.


Did you install from source/binaries/apt-get, yum or other package updater?
Have you tried v1.6.3?

Andy.

Mark Williamson wrote:

Im missing the table backup/restore on PGadmin 1.6.2 in Linux


Sorry if this is a faq but a cursory look at the bug list didnt reveal 
anything.


Mark

---(end of broadcast)---
TIP 6: explain analyze is your friend

!DSPAM:37,460c1de2103004269410021!





---(end of broadcast)---
TIP 4: Have you searched our list archives?

  http://archives.postgresql.org

[Fwd: Re: [pgadmin-support] No backup/restore for Linux?]

[Andy Shellam]

*OP's original e-mail forwarded to list*

 Original Message 
Subject:Re: [pgadmin-support] No backup/restore for Linux?
Date:   Thu, 29 Mar 2007 17:20:14 -0500
From:   Mark Williamson <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
References: 
<[EMAIL PROTECTED]> 
<[EMAIL PROTECTED]>




On the windows client, when you right click on a table, you have
"Backup" "Restore" under Maintenance

Im using Mandriva Linux, I got 1.6.2 from the distro and there is no
such options on the same context menu.

Also,

I'm mildly interested in contributing bug fixes however I would like
to know how to get into the club :)  what i plan on doing first of all
is getting the environment all setup and running here (I have Visual
Studio 2006 as well as the Linux environment at my disposal), then
test out some code fix ideas.  If I'm able to actually do anything
perhaps I'll post my feedback and patches here?

Some things that REALLY need work are the query editor (find/replace
is useless), and various other annoyances.

I'd just like to see pgAdmin graduate to the level of SQLyog

Mark

!DSPAM:37,460c3ba4103001413313393!




---(end of broadcast)---
TIP 5: don't forget to increase your free space map settings

Re: [pgadmin-support] Server not listening

[Andy Shellam]

Also from the machine you tried the ping from, do telnet  
5432 - see if that connects.

Something's definitely not quite correct on the server-side.

Check any firewalls (particularly the Windows Firewall if running an XP 
SP2 or 2003 client machine.)


Andy

Raymond O'Donnell wrote:

On 18/04/2007 21:29, GeorgeHeller wrote:


I have changed the postgresql.conf file to have listen_addresses='*' and
port=5432, and have restarted the server. 


if you have psql on another computer, try using it to connect to the 
server and see what happens.


psql -h (serveraddress) -U (username) -d (databasename) etc.

Ray.

---
Raymond O'Donnell, Director of Music, Galway Cathedral, Ireland
[EMAIL PROTECTED]
---

---(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

!DSPAM:37,4626969389293030030429!





---(end of broadcast)---
TIP 6: explain analyze is your friend

Re: [pgadmin-support] Server not listening

[Andy Shellam]

Hi George,

From the server's console, do "telnet  5432."
Make sure to use the server's remote IP, not localhost.  If that fails, 
your PostgreSQL is not listening on that port correctly.  If it 
succeeds, then you've got a firewall problem.


If it's PostgreSQL isn't listening, make sure you have done a restart 
(not just a reload) since making the chance in your configuration file 
(just to make sure, if you can, stop then start it.)  Also check you are 
editing the correct file!  (I.e. the one in the same cluster directory 
that PostgreSQL is starting.)


Andy.

George Heller wrote:

Hi,
 
I tried a telnet, and it doesnt work. So atleast now I know there is 
something wrong with the server side, but I dont quite know what to do 
next. Any suggestions?
 
Is there some particular setup that needs to be done? I have disabled 
the Windows Firewall.
 
Thanks.

George

*/Andy Shellam <[EMAIL PROTECTED]>/* wrote:

Also from the machine you tried the ping from, do telnet
5432 - see if that connects.
Something's definitely not quite correct on the server-side.

Check any firewalls (particularly the Windows Firewall if running
an XP
SP2 or 2003 client machine.)

Andy

Raymond O'Donnell wrote:
> On 18/04/2007 21:29, GeorgeHeller wrote:
>
>> I have changed the postgresql.conf file to have
listen_addresses='*' and
>> port=5432, and have restarted the server.
>
> if you have psql on another computer, try using it to connect to
the
> server and see what happens.
>
> psql -h (serveraddress) -U (username) -d (databasename) etc.
>
> Ray.
>
> ---
> Raymond O'Donnell, Director of Music, Galway Cathedral, Ireland
> [EMAIL PROTECTED]
> ---
>
> ---(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
>
>
>
>



Ahhh...imagining that irresistible "new car" smell?
Check out new cars at Yahoo! Autos. 
<http://us.rd.yahoo.com/evt=48245/*http://autos.yahoo.com/new_cars.html;_ylc=X3oDMTE1YW1jcXJ2BF9TAzk3MTA3MDc2BHNlYwNtYWlsdGFncwRzbGsDbmV3LWNhcnM-> 
!DSPAM:37,4627d7de89291495521781! 



---(end of broadcast)---
TIP 5: don't forget to increase your free space map settings

Re: [pgadmin-support] [ADMIN] Parse the DF file to table

[Andy Shellam]

Firstly, I think this is a little in-depth for a mailing list, and 
reading the manual will certainly help you out :)


Secondly, what exactly are you trying to do?  As all I can see your 
script doing is reading the amount of disk space used on each device, 
and if it's greater than 90% used, e-mail an alert.


What out of this are you trying to capture into your database?  And how 
can you summarise it by day, week, month?


Andy.

Trula Thomas wrote:

Hi Andy, if you could help me with this task I would really appreciate.

Task:
1) Create table in psql
2) Write shell cript to get the disk space
  a) Run DF into file
  b) Parse the DF file to table
3) Create the report bae on SQL that allows summary by day, week or month.

I have the shell cript :
#!/bin/sh
df -H | grep -vE '^Filesystem|tmpfs|cdrom' | awk '{ print $5 " " $1 }' 
| while read output;

do
  echo $output
  usep=$(echo $output | awk '{ print $1}' | cut -d'%' -f1  )
  partition=$(echo $output | awk '{ print $2 }' )
  if [ $usep -ge 90 ]; then
echo "Running out of space \"$partition ($usep%)\" on $(hostname) 
as on $(date)" |

 mail -s "Alert: Almost out of disk space $usep%" [EMAIL PROTECTED]
  fi
done

Please help if you can.

Thanks ~ Trula

*/Andy Shellam <[EMAIL PROTECTED]>/* wrote:

I think you need to provide more information on what you're trying to
do, and the version of PostgreSQL you're using, which environment etc.

If you're talking about reading a comma-delimited or tab-delimited
text
file, then see the COPY FROM command.
http://www.postgresql.org/docs/8.2/static/sql-copy.html

Andy.

Trula Thomas wrote:
> Hello, please show me how to parse the disk file to table.
> Thank you in advance.
> Trula
>
>

> Ahhh...imagining that irresistible "new car" smell?
> Check out new cars at Yahoo! Autos.
>
>



Ahhh...imagining that irresistible "new car" smell?
Check out new cars at Yahoo! Autos. 
<http://us.rd.yahoo.com/evt=48245/*http://autos.yahoo.com/new_cars.html;_ylc=X3oDMTE1YW1jcXJ2BF9TAzk3MTA3MDc2BHNlYwNtYWlsdGFncwRzbGsDbmV3LWNhcnM-> 
!DSPAM:37,462bf80789291630450605! 



---(end of broadcast)---
TIP 3: Have you checked our extensive FAQ?

  http://www.postgresql.org/docs/faq

Re: [pgadmin-support] Server not listening

[Andy Shellam]

Hi George,

When you add a connection to PgAdmin you specify the port details and 
the host name to connect to. 
If the connection is already there, open it's properties to check the 
settings.  Did the telnet from your XP machine succeed, or fail?  Do you 
have any firewalls running on the server (e.g. 
iptables/netfilter/shorewall (Linux systems) or IP filter (BSD systems))?


It's not a pg_hba.conf problem (yet) as that'd give you a different 
failure message.


Andy.

George Heller wrote:
Well, I am not really able to verify that, as the PgAdmin doesn't 
connect in the first place. So the connections and authentication is 
disabled.
 
I think I know that the server is listening at the default port 5432, 
and I have switched off my windows firewall too, but I am not too sure 
what I can do next.
 
Any suggestions?
 
Thanks.

George

*/Melvin Davidson <[EMAIL PROTECTED]>/* wrote:

Check that the value of Port in the pgadmin connection properties
matches the value of "port " in postgresql.conf on the server.
 
In should be located under the

# CONNECTIONS AND AUTHENTICATION
section of postgresql.conf


*From:* [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] *On Behalf Of
*George Heller
*Sent:* Friday, April 20, 2007 1:27 PM
*To:* [EMAIL PROTECTED]
*Cc:* pgadmin-support@postgresql.org
*Subject:* Re: [pgadmin-support] Server not listening

Hi,
 
Thanks for the reply. I did a telnet using the server's remote IP,

and it worked! So I am assuming now that it is a firewall
problem But I have turned off the windows firewall from my
system, I have tried restarting the system too. No luck!
 
I have changed the pg_hba.conf to have the ip address of my

windows machine. I have restarted the postgres server too. I am
thinking that really isnt the problem, since my telnet, ping etc.
all go through fine.
 
Anything else I can try? Really looking forward to getting around

this problem!
 
    Thanks!

George

*/Andy Shellam <[EMAIL PROTECTED]>/* wrote:

Hi George,

From the server's console, do "telnet 5432."
Make sure to use the server's remote IP, not localhost. If
that fails,
your PostgreSQL is not listening on that port correctly. If it
succeeds, then you've got a firewall problem.

If it's PostgreSQL isn't listening, make sure you have done a
restart
(not just a reload) since making the chance in your
configuration file
(just to make sure, if you can, stop then start it.) Also
check you are
editing the correct file! (I.e. the one in the same cluster
directory
that PostgreSQL is starting.)

Andy.

George Heller wrote:
> Hi,
>
> I tried a telnet, and it doesnt work. So atleast now I know
there is
> something wrong with the server side, but I dont quite know
what to do
> next.. Any suggestions?
>
> Is there some particular setup that needs to be done? I have
disabled
    > the Windows Firewall.
>
> Thanks.
> George
>
> */Andy Shellam /* wrote:
>
> Also from the machine you tried the ping from, do telnet
> 5432 - see if that connects.
> Something's definitely not quite correct on the server-side.
>
> Check any firewalls (particularly the Windows Firewall if
running
> an XP
> SP2 or 2003 client machine.)
>
> Andy
>
> Raymond O'Donnell wrote:
> > On 18/04/2007 21:29, GeorgeHeller wrote:
> >
> >> I have changed the postgresql.conf file to have
> listen_addresses='*' and
> >> port=5432, and have restarted the server.
> >
> > if you have psql on another computer, try using it to
connect to
> the
> > server and see what happens.
> >
> > psql -h (serveraddress) -U (username) -d (databasename) etc.
> >
> > Ray.
> >
> >
---
> > Raymond O'Donnell, Director of Music, Galway Cathedral,
Ireland
> > [EMAIL PROTECTED]
> >
---
> >
> > 

Re: [pgadmin-support] Server not listening

[Andy Shellam]

Hi George,

OK the fact you cannot telnet from your XP machine to the server's 
PostgreSQL port now suggests it's a problem getting to the server port.
Checking for the existence of a firewall is an ambiguous question I'm 
afraid!  There's not only the case of if there's a software firewall, 
but is there a router between you and the server that's filtering out 
other traffic?


What version of Linux are you running on the server? 
Who originally set the server up? 
Can they not tell you if there's a firewall on it?

Who set up the networks between you and the server?
Is there a router between you and the server, or a hardware firewall?

One thing that's just struck me that you can do in the interim (which is 
actually better security but doesn't really answer your question) 
because you have SSH access, is to tunnel PostgreSQL over SSH.  This is 
actually what I do, my firewall doesn't let anyone but the server 
connect to PostgreSQL.


I take it you're using PuTTY to connect via SSH to the server?  If so, 
see this link to set up a tunnel.

http://docs.cs.byu.edu/docs/sshtunnels/3.php

In the tunneling setup in PuTTY (as described in the link above), set 
the following:


Source port: 5432
Destination: 127.0.0.1:5432
Set it as Local, and Auto

Add the tunnel, then save the connection.  Now when you connect to your 
server via SSH, you'll have a port listening on 5432 on your local 
machine.  Whatever you send/receive from this port will be tunneled to 
the server over SSH.


It's then as easy as instructing PgAdmin to connect to "localhost" on 
port 5432, in the background it's actually connecting to your server.


HTH

Andy.


George Heller wrote:
My XP machine is not in the same subnet as the server, but I have the 
IP address of my XP machine specified in the pg_hba.conf file. Is that 
not enough to let me access the database from my XP machine?
 
I am able to do an SSH from my XP machine to the server, and also can 
access psql using it.
 
I am also able to ping from my XP machine to the server, and this goes 
through fine.
 
George


*/Raymond O'Donnell <[EMAIL PROTECTED]>/* wrote:

On 24/04/2007 06:43, George Heller wrote:

> Ok, I tried a telnet from the command prompt of my XP machine,
to the
> linux server address on port 5432, something like,
>
> C:\> telnet 132.141.101.1 5432
>
> And this did 'not' go through. It said could not open connection to
> host, connect failed.

Well, this sounds like a network problem, as others have suggested.
Check that your XP machine and the machine with the PostgreSQL server
are on the same subnet, or are otherwise able to talk to each
other. Are
you able to use telnet or ssh to open a terminal session from one
to the
other? Did you try using psql to connect to the DBMS?

Ray.

---
Raymond O'Donnell, Director of Music, Galway Cathedral, Ireland
[EMAIL PROTECTED]
---



Ahhh...imagining that irresistible "new car" smell?
Check out new cars at Yahoo! Autos. 
 
!DSPAM:37,462e0ab389291241012752! 



---(end of broadcast)---
TIP 3: Have you checked our extensive FAQ?

  http://www.postgresql.org/docs/faq

Re: [pgadmin-support] Server not listening

[Andy Shellam]

Hi George,

Make sure you're using the latest PuTTY (something like 0.59 if I 
remember rightly.)
Then from the screen that opens when you run PuTTY, Load your saved 
settings.
On the right, browse to SSH, then Tunnels - add the settings in there 
(your tunnel should be shown in the "Forwarded Ports" dialog when you've 
added it.)


Then click back to Session (on the top-right) and save your settings 
profile.

Then connect and login to your server.

Don't open two SSH connections with the forwarded tunnel active, or it 
will do strange things.
You can then connect to your PostgreSQL server by connecting to 
localhost:5432 within PgAdmin.


Only the PostgreSQL port will be forwarded, so you cannot connect to SSH 
on localhost (unless of course you run a local SSH server on your XP 
machine ;))


If that doesn't work, close your SSH session, change the forwarded IP 
address in your tunnel configuration to your server's remote IP address, 
then re-connect.


Andy.


George Heller wrote:

Hi,
 
Thanks for that mail. I tried to follow the steps to create a tunnel, 
but when I add the connection, I dont really see an option to Save the 
settings. So make the changes and log in to my server with the actual 
hostname, it logs me in. I open another session on Putty, and the 
changes I made in the port forwarding are gone, I make the changes 
again, and try to log in using 'localhost' this time, it says 
Connection refused.
 
I also tried logging into PgAdmin using localhost, but it gave me the 
same error as before, only this time it said ip address 127.0.0.1
 
Thanks.

George.

*/Andy Shellam <[EMAIL PROTECTED]>/* wrote:

Hi George,

OK the fact you cannot telnet from your XP machine to the server's
PostgreSQL port now suggests it's a problem getting to the server
port.
Checking for the existence of a firewall is an ambiguous question I'm
afraid! There's not only the case of if there's a software firewall,
but is there a router between you and the server that's filtering out
other traffic?

What version of Linux are you running on the server?
Who originally set the server up?
Can they not tell you if there's a firewall on it?
Who set up the networks between you and the server?
Is there a router between you and the server, or a hardware firewall?

One thing that's just struck me that you can do in the interim
(which is
actually better security but doesn't really answer your question)
because you have SSH access, is to tunnel PostgreSQL over SSH.
This is
actually what I do, my firewall doesn't let anyone but the server
connect to PostgreSQL.

I take it you're using PuTTY to connect via SSH to the server? If so,
see this link to set up a tunnel.
http://docs.cs.byu.edu/docs/sshtunnels/3.php

In the tunneling setup in PuTTY (as described in the link above), set
the following:

Source port: 5432
Destination: 127.0.0.1:5432
Set it as Local, and Auto

Add the tunnel, then save the connection. Now when you connect to
your
server via SSH, you'll have a port listening on 5432 on your local
machine. Whatever you send/receive from this port will be tunneled to
the server over SSH.

It's then as easy as instructing PgAdmin to connect to "localhost" on
port 5432, in the background it's actually connecting to your server.

HTH

Andy.


George Heller wrote:
> My XP machine is not in the same subnet as the server, but I
have the
> IP address of my XP machine specified in the pg_hba.conf file.
Is that
> not enough to let me access the database from my XP machine?
>
> I am able to do an SSH from my XP machine to the server, and
also can
> access psql using it.
>
> I am also able to ping from my XP machine to the server, and
this goes
> through fine.
>
> George
>
> */Raymond O'Donnell /* wrote:
>
> On 24/04/2007 06:43, George Heller wrote:
>
> > Ok, I tried a telnet from the command prompt of my XP machine,
> to the
> > linux server address on port 5432, something like,
> >
> > C:\> telnet 132.141.101.1 5432
> >
> > And this did 'not' go through. It said could not open
connection to
> > host, connect failed.
>
> Well, this sounds like a network problem, as others have suggested.
> Check that your XP machine and the machine with the PostgreSQL
server
> are on the same subnet, or are otherwise able to talk to each
> other. Are
> you able to use telnet or ssh to open a terminal session from on

Re: [pgadmin-support] Server not listening

[Andy Shellam]

gs me in. I open another session on
Putty, and the changes I made in the port forwarding are gone, I
make the changes again, and try to log in using 'localhost' this
time, it says Connection refused.
 
I also tried logging into PgAdmin using localhost, but it gave me

the same error as before, only this time it said ip address 127.0.0.1
 
Thanks.

George.

*/Andy Shellam <[EMAIL PROTECTED]>/* wrote:

 [snip] 

!DSPAM:37,462fa73a89291812814777! 



---(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] Server not listening

[Andy Shellam]

Joris Dobbelsteen wrote:

-Original Message-
From: Andy Shellam [mailto:[EMAIL PROTECTED] 
Sent: woensdag 25 april 2007 21:25

To: Joris Dobbelsteen
Cc: George Heller; pgadmin-support@postgresql.org
Subject: Re: [pgadmin-support] Server not listening

I concur, but just so you know I suggested SSH so George can 
get up and running quickly while diagnosing the problems later 
as it requires a lot of information he doesn't seem to have.  
We've already established he has SSH access so it seemed an 
obvious way to connect so he could actually begin to use PostgreSQL.



Hopefully you took no offence while I took this a sharp turn.
  
No, not at all.  I was just explaining my reasoning, as it seemed 
obvious George wasn't going to be able to get this information any time 
soon.

I agree that this would be probably a good idea to get it working.
Alternatively it might seem easier to have a temporary set up on the
local computer, if feasable.
  
True, but his server's running Linux, so you've got the problem of 
transferring the data from Windows to Linux when he gets it working, 
which depending on the amount of data, could be trivial, or not :)

[snip]

- Joris Dobbelsteen


!DSPAM:37,462fba1989295324916066!


  



---(end of broadcast)---
TIP 4: Have you searched our list archives?

  http://archives.postgresql.org

[pgadmin-support] Restore dialog

[Andy Shellam]

Hi Dave,

A quick suggestion for PgAdmin's "Restore database" dialog.

When you restore a database, you select your file and options, then 
click "OK" and the restore does it's thing and finishes, showing you the 
output from pg_restore. 
However the button stays as "OK".  So you instinctively click it again 
to close the dialog, and it tries to do the restore again - you have to 
click Cancel or close the window instead.


Can this be changed so it's like the backup, where you click OK to start 
the backup, but once it's finished, the OK button changes to "Done" and 
closes the window when you click it.


Thanks

Andy.

---(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] OK button on restore

[Andy Shellam]

Yep I agree, with pg_restore, warnings also generate a non-zero return 
code, but the restore does complete successfully, so this is mis-leading.
An example is "language  already exists" - pg_restore just throws a 
warning to let you know this, but the restore is successful.


Perhaps what might work better is a message box - if you've already 
performed a restore but it returned non-zero, and OK is pressed again in 
the same dialogue box, throw up a message saying something like "you've 
already attempted a restore, are you sure you want to run it again?"


Andy.

Luiz K. Matsumura wrote:
I agree with Pierce, instead of OK buttom we can have another message 
like "start restore" or just "restore".
I don't remember how much times inadvertently press OK buttom to close 
this screen. (Yeah, I was thinking that this occur only with me :P )

This is a little change, but will help a lot.

TIA.


Pierce Tyler wrote:
That makes sense. But it still might be helpful to add an additional 
safeguard (like a pop-up message, for example). I've seen cases where 
the log returns only one error--something insignificant--and the user 
decides they can live with it. So they click OK, thinking they're 
exiting the screen, moving on. But instead they may have 
inadvertently corrupted their database.



Dave Page wrote:

Pierce Tyler wrote:
This may be more of a feature request/suggestion than a bug. But 
here's

the issue: After finishing a restore using the Windows version (tested
in 1.6.3, but was also present in 1.4.x), if you click the "OK" button
when you're done, the restore process runs a 2d time--which is not
desirable. I've used the program enough to know I should select 
"CANCEL"

instead. But the distinction between OK and CANCEL (or "DONE", which I
believe I've seen in some versions) is not totally clear. The bottom
line is it's far too easy for a user to click OK thinking they're 
doing

the right thing, when in fact it's not the right thing to do.


If the restore doesn't return a success code the button stays at OK so
you can tweak the options and try again. If it does return a success
code (zero), the button changes to Done. The same applies to the backup
dialogues.

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] OK button on restore

[Andy Shellam]

That's great Dave, I'm sure it'll please many folks!!

Thanks

Andy.

Dave Page wrote:

Andy Shellam wrote:
  

Yep I agree, with pg_restore, warnings also generate a non-zero return
code, but the restore does complete successfully, so this is mis-leading.
An example is "language  already exists" - pg_restore just throws a
warning to let you know this, but the restore is successful.

Perhaps what might work better is a message box - if you've already
performed a restore but it returned non-zero, and OK is pressed again in
the same dialogue box, throw up a message saying something like "you've
already attempted a restore, are you sure you want to run it again?"



Now thats a solution I'm happy with - I've added code to do this, if a
restore (or backup) is attempted from the same dialog invocation, with
the same filename as previously used.


Thanks, Dave

!DSPAM:37,466eaba6343941575920893!


  



---(end of broadcast)---
TIP 4: Have you searched our list archives?

  http://archives.postgresql.org

[pgadmin-support] New sequence in 1.8.1

[Andy Shellam]

Hi team,

I've noticed a small bug in 1.8.1 on Windows XP (SP2).

If I create a new table, and add a new serial column to it before OK'ing the
"create table" dialog, the "sequence" drop-down remains disabled for the
column.

If I create a table, and OK the dialog without any columns in, then go back
and modify the table and add a new serial column to it, the "sequence"
drop-down is enabled correctly.

Regards,

Andy

Re: [pgadmin-support] New sequence in 1.8.1

[Andy Shellam]

Hi Dave,

I see your point about it not doing anything after the column is created, as
a serial column is just an integer column with a new default value.  I liked
the idea of being able to specify a different sequence to use with the
serial column, but having said that I can't think of many uses where you'd
want to!

Unless you can make the sequence combo of any use (e.g. to change the
default sequence used when creating the column) I'd say get rid of it!

Thanks,

Andy

On 1/14/08, Dave Page <[EMAIL PROTECTED]> wrote:
>
> On 14/01/2008, Guillaume Lelarge <[EMAIL PROTECTED]> wrote:
> > Andy Shellam wrote:
> > > I've noticed a small bug in 1.8.1 on Windows XP (SP2).
> > >
> > > If I create a new table, and add a new serial column to it before
> OK'ing
> > > the "create table" dialog, the "sequence" drop-down remains disabled
> for
> > > the column.
> > >
> > > If I create a table, and OK the dialog without any columns in, then go
> > > back and modify the table and add a new serial column to it, the
> > > "sequence" drop-down is enabled correctly.
> > >
> >
> > I just had a quick look and you're right. Behaviour is different when
> > table is already created. I think we need to fix this so the behavior
> > remains consistent. I'm not sure what value has the ""
> > text. So should we add this text when we add a serial column at table
> > creation time or should we suppress this text ?
>
> Yeah, that box just doesn't work when the dialogue is called from the
> table dialogue (even when the control is enabled) - it tries to do
> things that just aren't possible given the way the two dialogues
> communicate. It also doesn't do anything when changing an existing
> column because at that point it thinks the column is an integer column
> with a default value.
>
> I'm of half a mind to remove the sequence combo box altogether.
>
> Thoughts?
>
> /D
>

[pgadmin-support] Show NULL values AS not working

[Andy Shellam]

Hi Dave and team,

Another slight bug (I think):

I have a table which has a column called "first_invalid" which should be a
timestamp if the record is invalid, or NULL if it's valid.
In PgAdmin I have the "Show NULL values as " option enabled, but it
still displays a blank cell for this column.

The reason why I think it may not be a bug, is I tried doing this:

"SELECT COALESCE(first_invalid, '') AS first_invalid FROM table"

but PostgreSQL threw it out because "" is not a valid timestamp -
instead I had to do:

"SELECT COALESCE(first_invalid, '1900-01-01') AS first_invalid FROM table"

to prove the column is in fact NULL, and I do get: "1900-01-01 00:00:00+00"
for this record, but in the data entry grid, PgAdmin still displays it
blank.

Question: is this a bug, or intended behaviour?

Thanks,

Andy

Re: [pgadmin-support] Show NULL values AS not working

[Andy Shellam]

Hi guys,

A bit more info.

If I write a query manually (i.e. SELECT * FROM table) then the column shows
up as "" which is what I expect.
However, if I write click the table and hit the "View Data" menu option, the
column is blank.

Andy.

On 1/14/08, Andy Shellam <[EMAIL PROTECTED]> wrote:
>
> Hi Dave and team,
>
> Another slight bug (I think):
>
> I have a table which has a column called "first_invalid" which should be a
> timestamp if the record is invalid, or NULL if it's valid.
> In PgAdmin I have the "Show NULL values as " option enabled, but it
> still displays a blank cell for this column.
>
> The reason why I think it may not be a bug, is I tried doing this:
>
> "SELECT COALESCE(first_invalid, '') AS first_invalid FROM table"
>
> but PostgreSQL threw it out because "" is not a valid timestamp -
> instead I had to do:
>
> "SELECT COALESCE(first_invalid, '1900-01-01') AS first_invalid FROM table"
>
> to prove the column is in fact NULL, and I do get: "1900-01-01
> 00:00:00+00" for this record, but in the data entry grid, PgAdmin still
> displays it blank.
>
> Question: is this a bug, or intended behaviour?
>
> Thanks,
>
> Andy
>

Re: [pgadmin-support] Show NULL values AS not working

[Andy Shellam]

Hi Dave

Ah right OK, I didn't realise the "Query" tab was just for SQL editor, I
thought it was for the data entry grids as well.

Thanks for clearing that up.


> instead I had to do:
> >
> > "SELECT COALESCE(first_invalid, '1900-01-01') AS first_invalid FROM
> table"
> >
> > to prove the column is in fact NULL, and I do get: "1900-01-01
> 00:00:00+00"
> > for this record, but in the data entry grid, PgAdmin still displays it
> > blank.
>
> That doesn't prove it's null - it proves it's null OR 1900-01-01
> 00:00:00+00. However, the  output option is onlt for the Query
> Tool. The data entry grid always displays an empty cell for NULL, ''
> for a blank string, and \'\' for a pair or single quotes. From the
> docs:



I knew it was NULL cause the table only had 1 row in it, and I'd purposely
set it to NULL through a query ;-)

Andy

Re: [pgadmin-support] Server not listening

[andy . shellam-lists]

Hi George,

As Joris said, we need you to try what he has suggested.
The fact you can now connect via SSH proves PostgreSQL is set up and
configured correctly, which would point to a firewall or intermediate router
blocking your connections.

On the server (as root), do "iptables -L" or "/usr/local/sbin/iptables -L" if
the previous doesn't work, and post the full output so we can see if a
software firewall is blocking.

And please try and get some information about your network - who set the
server up, is there a hardware firewall or router firewall in between you and
the server, etc.

Thanks

Andy.

George Heller <[EMAIL PROTECTED]> wrote:

> Hi,
>
>   Ok, I have reached to the point where the SSH tunelling works, and I am
able
> to connect using it to PgAdmin. But I still want to know what exactly is
wrong
> with the other setup.
>
>   I just came across this in the postgres documentation, about starting the
> postmaster with an -i option, if you want your server to accept TCP/IP
> connections. 
>   http://www.postgresql.org/docs/7.4/static/postmaster-start.html
>
>   I just used the -D option as specified, to start the server. Is it
necessary
> to use the -i option so that my server can listen, or is the documentation
just
> too old? If yes, what is the syntax for the same?
>
>   Thanks.
>   George.
> 
> Joris Dobbelsteen <[EMAIL PROTECTED]> wrote:
>   >-Original Message-
> >From: Andy Shellam [mailto:[EMAIL PROTECTED] 
> >Sent: woensdag 25 april 2007 21:25
> >To: Joris Dobbelsteen
> >Cc: George Heller; pgadmin-support@postgresql.org
> >Subject: Re: [pgadmin-support] Server not listening
> >
> >I concur, but just so you know I suggested SSH so George can 
> >get up and running quickly while diagnosing the problems later 
> >as it requires a lot of information he doesn't seem to have. 
> >We've already established he has SSH access so it seemed an 
> >obvious way to connect so he could actually begin to use PostgreSQL.
> 
> Hopefully you took no offence while I took this a sharp turn.
> 
> I agree that this would be probably a good idea to get it working.
> Alternatively it might seem easier to have a temporary set up on the
> local computer, if feasable.
> 
> [snip]
> 
> - Joris Dobbelsteen
> 
> 
> 
>
> -
> Ahhh...imagining that irresistible "new car" smell?
>  Check outnew cars at Yahoo! Autos.
> 
> !DSPAM:37,4636eb7689291063614559!
> 

_
DISCLAIMER

This e-mail was sent through a Mail Network server.
The Mail Network accepts no liability for it's content.




---(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] Doubt

[andy . shellam-lists]

I presume you mean when you're creating a new connection?

If PostgreSQL is running on a Windows machine, this is the name of the service
it's running under.  Should be left blank for Unix machines.

Account name?  Do you mean username?  This is a user that's been added to the
PostgreSQL server (or the default, postgres.)



<[EMAIL PROTECTED]> wrote:

> what is mean by service name and account name, how to create it..
> 
> !DSPAM:37,4637358f89292922115346!
> 

_
DISCLAIMER

This e-mail was sent through a Mail Network server.
The Mail Network accepts no liability for it's content.




---(end of broadcast)---
TIP 3: Have you checked our extensive FAQ?

   http://www.postgresql.org/docs/faq

Re: [pgadmin-support] Restore dialog

[andy . shellam-lists]

Ah OK thanks for clearing that up.

Whenever I do a restore, it always warns that the plpgsql language is already
present, hence returns with code 1.

Thanks

Andy.

Dave Page <[EMAIL PROTECTED]> wrote:

> Andy Shellam wrote:
> > Hi Dave,
> > 
> > A quick suggestion for PgAdmin's "Restore database" dialog.
> > 
> > When you restore a database, you select your file and options, then
> > click "OK" and the restore does it's thing and finishes, showing you the
> > output from pg_restore. However the button stays as "OK".  So you
> > instinctively click it again to close the dialog, and it tries to do the
> > restore again - you have to click Cancel or close the window instead.
> > 
> > Can this be changed so it's like the backup, where you click OK to start
> > the backup, but once it's finished, the OK button changes to "Done" and
> > closes the window when you click it.
> 
> Hi Andy,
> 
> They actually do work the same - if the external process returns a
> non-zero value, it's assumed that you may want to try again with
> different options (or having tweaked the database) so the button doesn't
> change.
> 
> If zero is returned, the button changes to 'Done' because the task
> completed successfully.
> 
> Regards, Dave
> 
> !DSPAM:37,46486edb343942003256220!
> 
> 
> 

_
DISCLAIMER

This e-mail was sent through a Mail Network server.
The Mail Network accepts no liability for it's content.




---(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

[pgadmin-support] Empty tables show no field headings

[Andy Shellam (Mailing Lists)]

Hi,

I've just joined this list.
In v1.6.1, when I go to view the data for a table with no (zero) rows, I 
don't see the columns of the table and no place to key a new record.
The table does have a primary key, and when it's got rows in, I can edit 
and add new ones.


Steps to reproduce:

- Open a table with data in
- Delete all rows
- Close the table
- Re-open - get blank screen with no columns or "new row" placeholder

This is on Windows XP, pgAdmin version 1.6.1, PostgreSQL 8.1.5 server.

Thanks,

--
Andy Shellam
NetServe Support Team

the Mail Network
"an alternative in a standardised world"



---(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: Re : Re : Re : [pgadmin-support] No text for error messages only

[Andy Shellam (Mailing Lists)]

(I have read the the particulary annoying bug of empty tables not being editable is fixed in 1.6.2) 
  

Excellent, I'll be looking forward to that!


--
Andy Shellam
NetServe Support Team

the Mail Network
"an alternative in a standardised world"



---(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: Re : [pgadmin-support] No text for error messages only numbers

[Andy Shellam (Mailing Lists)]

I still can't reproduce it. My databases are also in UTF-8. Some are in
LATIN1. I tried with en and fr pgAdmin. I have no problem. But I'm using
1.6.2. Perhaps Dave already fixed it ?

Regards.
  

I was wondering - where are you using 1.6.2 from?
There's a serious bug in 1.6.1 where you cannot key new rows into a 
table that has a zero row-count, I've heard that's fixed in 1.6.2, but 
it isn't out yet?



Thanks

--
Andy Shellam
NetServe Support Team

the Mail Network
"an alternative in a standardised world"



---(end of broadcast)---
TIP 5: don't forget to increase your free space map settings

Re: [pgadmin-support] 1.6.1 and 1.7.0 rendering bug

[Andy Shellam (Mailing Lists)]

FYI,

This works fine on 1.6.1 on Windows XP - no problem.

Regards,

Andy.

Clodoaldo wrote:

When a function is selected in the object browser the function's
create script is shown in the properties tab meshed with the
properties values.

This happens in both 1.6.1 and 1.7.0 with wxGTK 2.8.0. It did not
happen in 1.4.x with wxGTK 2.6.

As I think it is hard to visualize I took a screenshot (127 KB):
http://fahstats.com/img/pgadmin_bug.png

I'm using FC5 i386, wxGTK 2.8.0 and the Gnome desktop.

Regards,



--
Andy Shellam
NetServe Support Team

the Mail Network
"an alternative in a standardised world"



---(end of broadcast)---
TIP 6: explain analyze is your friend

Re: [pgadmin-support] [ADMIN] DB problem

[Andy Shellam (Mailing Lists)]

Vinayak,

Please don't post twice to two different lists (four of the same posts 
to both pgsql-admin and pgadmin-support.)
This clearly isn't a problem with PG Admin - so don't clutter that list 
up, and don't multiple-post - it won't change anything posting twice, 
and if anything you'll only end up annoying people so they won't feel 
obliged to help you anyway.


In answer to your question, it took me 3 minutes to find this manual page:

http://www.postgresql.org/docs/7.3/static/runtime-config.html

There is no log_directory setting, but it is in 8.x 
(http://www.postgresql.org/docs/8.0/static/runtime-config.html), so your 
version doesn't support it.


It would be helpful if you consult the manual for your running version, 
not the current release, as features inevitably get added and others 
change.  And, as someone's already said, you should be thinking of 
upgrading to at minimum 8.1.


Andy.

[EMAIL PROTECTED] wrote:

Hi,
 
We are using PostgreSQL 7.3 version, installed in linux system. Only 
DB is getting shut down 3-4 times a day. From my application end I get 
"Sorry too many clients" error. 
Refering the FAQ I maximized the DB session limit to 200.
 
I think the logs are not enabled in my DB. So I set the following 
options in postgresql.con file
 
log_timestamp= true
log_directory=pg_log 
log_filename=%Y-%m-%d_%H%M%S.log 
log_disconnections=true
log_hostname=true   
log_statement=true
 
 
After restarting the system got the following error :
[EMAIL PROTECTED] root]# su postgres bash-2.05b$ postmaster -i -D 
/var/lib/pgsql/data FATAL: postgresql.conf:131: syntax error,
token="%" bash-2.05b$ postmaster -i -D /var/lib/pgsql/data FATAL: 
postgresql.conf:131: syntax error, token="%" bash-2.05b$ postmaster -i 
-D /var/lib/pgsql/data FATAL: postgresql.conf:131: syntax error, 
token="%" bash-2.05b$ postmaster -i -D /var/lib/pgsql/data FATAL: 
'log_directory' is not a valid option name bash-2.05b$ postmaster -i 
-D /var/lib/pgsql/data FATAL: 'log_directory' is not a valid option 
name bash-2.05b$ postmaster -i -D /var/lib/pgsql/data FATAL: 
'log_filename' is not a valid option name bash-2.05b$ postmaster -i -D 
/var/lib/pgsql/data FATAL: 'log_disconnections' is not a valid option 
name bash-2.05b$ postmaster -i -D /var/lib/pg


When you install the DB, the logs are enabled by default?
 
Would you pls tell me still what setting need to be done?
 
Thanks,

Vinayak V. Raikar
Extn : 143

!DSPAM:37,4590b56931941914011633! 



--
Andy Shellam
NetServe Support Team

the Mail Network
"an alternative in a standardised world"

p: +44 (0) 121 288 0832/0839
m: +44 (0) 7818 000834


---(end of broadcast)---
TIP 5: don't forget to increase your free space map settings

Re: [pgadmin-support] View all rows not updated properly if program

[Andy Shellam (Mailing Lists)]

Guy Rouillier wrote:
I'm using PgAdmin 1.6.1 against PG 8.2.0, both running on Windows XP.  
I have a test Java program that inserts and deletes rows into a single 
table; I vary the operation of the program by commenting out various 
parts.  Before running the program, I open a view window on this table 
by selecting "View all rows".  When I configure the program to just 
insert rows and click the refresh icon, all the inserted rows show up. 
If I configure the program to insert then delete *some* rows, when I 
click the refresh icon, the remaining rows are properly shown.  
However, if I configure the program to insert then delete all rows, 
clicking the refresh icon doesn't do anything.


If I go back to the main window and tell it to count the rows in this 
table, it correctly reports zero.  If I close the original view window 
then open a new one, it also correctly displays no data.




Hi Guy,

This is a known bug in this version which is apparently fixed in PgAdmin 
1.6.2 (not yet released) - also notice if you delete all rows in a 
table, close the original view and re-open, it shows no data - but you 
can't insert new rows either (no columns/new row placeholder.)


--
Andy Shellam
NetServe Support Team

the Mail Network
"an alternative in a standardised world"



---(end of broadcast)---
TIP 6: explain analyze is your friend

Re: [pgadmin-support] v.1.6.2: issue with truncated column comments.

[Andy Shellam (Mailing Lists)]

I prefer '...' to be honest.


  
Personally I prefer a mix of the two suggestions " ..." (space then 
three dots) lol but that's just me :)


--
Andy Shellam
NetServe Support Team

the Mail Network
"an alternative in a standardised world"



---(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] COPY my_table FROM STDIN

[Andy Shellam (Mailing Lists)]

If you have the data already in a text file, you can upload the text 
file to the server, then run "COPY  FROM " 
from within PgAdmin, but if you have psql access, then use that as it's 
much less hassle.


Dave Page wrote:

Laurent ROCHE wrote:
  

Hi,

I am trying to run a COPY my_table FROM STDIN from pgAdmin ... but I can not 
manage to get it to work !

It runs with psql !

Here is a short version of the command:
COPY xfrt.import_cpts FROM STDIN;
1DG 16930 7 JAN 071
2DG 25430 7 JAN 072
3DG 34617 7 JAN 073
\.

Am I missing something obvious ?



pgAdmin is not a console app - there is no easily usable stdin so you
cannot use COPY.

Regards, Dave.

---(end of broadcast)---
TIP 4: Have you searched our list archives?

   http://archives.postgresql.org

!DSPAM:37,45addcd5137102060715345!


  



--
Andy Shellam
NetServe Support Team

the Mail Network
"an alternative in a standardised world"

p: +44 (0) 121 288 0832/0839
m: +44 (0) 7818 000834


---(end of broadcast)---
TIP 2: Don't 'kill -9' the postmaster

Re: [pgadmin-support] installing pgAdmin3 1.6.2 on FC6

[Andy Shellam (Mailing Lists)]

Willy-Bas Loos wrote:

Ok thanks, guess i missed that one :x
So after i upgraded wxWidgets, it says i need to upgrade to libpq.so.5.
But i can't upgrade, because all kinds of software (i.e. 
postgresql-contrib) still depends on libpq.so.4 , because i'm running 
PostgreSQL 8.1.6


It's not necesarry to upgrade the backend for a new pgAdmin, or is it?
I know that on Windows it isnt't, why should it be necessary on Linux?


On Windows I think it is necessary, as PgAdmin has it's own libpq.dll - 
my version from 1.6.2 on Windows XP is "8.2.0.6338", so is obviously 
from the 8.2.0 series of PostgreSQL, which would equate to libpq.so.5 on 
Linux/Unix.  The server doesn't have to be upgraded, but the client 
library PgAdmin uses evidently does.


I don't know whether the following would work (I've done a similar thing 
in the past), I know it's nasty and crude, but it might work?
Download the source of PostgreSQL 8.2.x, and build it (./configure && 
make), but don't do make install.
Find the libpq.so.5 file from the newly-built source tree and place it 
in /lib, then sym-link /usr/lib/libpq.so.5 and /usr/local/lib/libpq.so.5 
to it.


Andy.

---(end of broadcast)---
TIP 5: don't forget to increase your free space map settings

Re: [pgadmin-support] Cannot connect to one specific postgres database

[Andy Shellam (Mailing Lists)]

Can you connect to it OK using psql on the server's console?
If you can, try dumping the database using pg_dump, then restore it as a 
different database and try connecting via PgAdmin to the new copy.



Matt Busby wrote:


Hello,

I am having trouble connecting to one specific database on my server. 
I can connect to the server via pgadmin and have pgadmin display 7 or 
8 databases I have running on the server. I can successfully connect 
to all of the databases except one. This particular database I am 
trying to connect to will just cause pgadmin to hang/crash


I have been using pgadmin for over 2 years to connect to this 
particular database that wont connect now. This just started happening 
a week ago and is frustrating me so bad! I have 
installed/reinstalled/uninstalled about every version on pgadmin with 
no success. I restarted postgres on the server with no success…


My server is running linux, and I am using windows version of pgadmin…

I WOULD REALLY APPRECIATE ANY HELP!!! THANKS SO MUCH!!!

Matt Busby

!DSPAM:37,45b5078b118211361817358! 



---(end of broadcast)---
TIP 5: don't forget to increase your free space map settings

Re: [pgadmin-support] Cannot connect to one specific postgres database

[Andy Shellam (Mailing Lists)]

Melvin,

Your understanding of how to set up a PostgreSQL server is wrong.
One server process (it was called the postmaster up to 8.1, since 8.2 
it's now called the Server process) can run any number of databases, you 
don't need multiple postmasters for multiple databases or your server is 
going to die quickly when you start adding more and more databases, not 
to mention the admin overhead of managing all the ports, and handling 
backups.


Using PgAdmin you connect to a particular server, connecting to the 
"postgres" database by default, then once you're connected to a 
PostgreSQL server, you choose which database/s to connect to.


Melvin Davidson wrote:
When you say "The site that is using the database is also running 
fine", Do you mean users are accessing

that database? If so, that check the port # you are using to connect.

This should be 5432 unless specifically changed during the build.
You might also try adding a new server connection to that database in 
pgadmin.
If the OP can connect to one database, he should be able to connect to 
another on the same server.
postmaster is the postgresql process that is needed to access the 
database.

Telnet to the server and do
ps -ef | grep postmaster
You should see something like
admin 2986 1 0 Jan12 ? 00:00:00 
/home/pgsql/postgresql-8.0.6/bin/postmaster
There are various processes for PostgreSQL, such as the auto-vacuum, 
stats-gatherer and background writer processes.

You will have a process for each database on a separate port.
No - if yours is set up this way, your server is going to be 
unnecessarily overloaded. One PostgreSQL postmaster/server process can 
run any number of databases on one port. It's only advisable to run more 
than one PostgreSQL server process on different ports if you want to run 
two different versions of PostgreSQL, or want to dump one set of 
databases to a different server (popular during a major version upgrade.)
If all postmaster(s) are running, then perhaps someone or 
something(gremlins) :) has modified the

pg_hba.conf file in the $PGDATA directory?
If the OP can connect to one database on the same server, there's no 
reason (aside from data corruption) why he shouldn't be able to connect 
to the required one, especially if nothing has changed - he'd get an "no 
pg_hba.conf entry for  if the pg_hba.conf file was 
mis-configured.


I'd advise the OP to either turn on debug logging in PgAdmin and 
re-create the crash, or dump the database from the server, restore as a 
different database on the same machine and try to connect to it again.
Matt, if you follow this method, it won't take the database down as long 
as you restore the dump to a different database name. If it works, I'd 
then advise to dump the original database again, drop it and re-create 
it. That will take it down for as long as the dump takes place.


Hope this helps!

Andy.


*From:* Matt Busby [mailto:[EMAIL PROTECTED]
*Sent:* Monday, January 22, 2007 12:10 PM
*To:* Melvin Davidson
*Cc:* pgadmin-support@postgresql.org
*Subject:* RE: [pgadmin-support] Cannot connect to one specific 
postgres database on a server


I can telnet to the database and query the database…. The site that is 
using the database is also running fine


Not sure what postmaster is…. How can I check if its running? I did a 
google search for it, but not sure how to check it on my postgres db 
server


I don’t get any errors using telnet … I can access the db every other 
way it seems, just using postgres


If I restore/rebuild the db, will that cause the database to go down 
at all? I will try anything to get pgadmin working with the db… it 
makes my life SOOO much easier!


Thanks very much for taking the time to help me with this issue! Much 
appreciated!


Matt



---(end of broadcast)---
TIP 5: don't forget to increase your free space map settings

Re: [pgadmin-support] Cannot connect to one specific postgres database

[Andy Shellam (Mailing Lists)]

Melvin Davidson wrote:

Yes, you are correct, but you can have multiple _clusters_ with
different ports,
so there would a separate postmaster for each cluster on a
server/machine with 
a different port. 
  


Yes, you can, but the way you've worded your response was that you have 
one postmaster process per _database_, which isn't correct.  A cluster 
is a group of databases, not one, therefore your response to the OP was 
misleading.

Keep in mind the port for the database was not specified in the original
description
so it s entirely possible the unaccessible database was due to the
postmaster for that
port being down.
  


The OP said they can access other databases on the same server OK, plus 
PgAdmin wouldn't crash - they'd get a "the server is not listening..." 
message.

BTW, we do have several servers/systems/machines running multiple
postmasters on multiple ports
so even of my "understanding" of postgresql is different than yours,
I must be doing something right. :)
  


If you have legitimate reasons for doing so, fine, but I was responding 
to the way you worded your question, which was you were saying you have 
one process per port per database, which is by no means ideal.


Regards

Andy.

-Original Message-
From: Andy Shellam (Mailing Lists)
[mailto:[EMAIL PROTECTED] 
Sent: Monday, January 22, 2007 2:35 PM

To: Melvin Davidson
Cc: Matt Busby; pgadmin-support@postgresql.org
Subject: Re: [pgadmin-support] Cannot connect to one specific postgres
database on a server

Melvin,

Your understanding of how to set up a PostgreSQL server is wrong.
One server process (it was called the postmaster up to 8.1, since 8.2
it's now called the Server process) can run any number of databases, you
don't need multiple postmasters for multiple databases or your server is
going to die quickly when you start adding more and more databases, not
to mention the admin overhead of managing all the ports, and handling
backups.

Using PgAdmin you connect to a particular server, connecting to the
"postgres" database by default, then once you're connected to a
PostgreSQL server, you choose which database/s to connect to.

Melvin Davidson wrote:
  
When you say "The site that is using the database is also running 
fine", Do you mean users are accessing that database? If so, that 
check the port # you are using to connect.


This should be 5432 unless specifically changed during the build.
  
You might also try adding a new server connection to that database in 
pgadmin.


If the OP can connect to one database, he should be able to connect to
another on the same server.
  
postmaster is the postgresql process that is needed to access the 
database.

Telnet to the server and do
ps -ef | grep postmaster
You should see something like
admin 2986 1 0 Jan12 ? 00:00:00
/home/pgsql/postgresql-8.0.6/bin/postmaster


There are various processes for PostgreSQL, such as the auto-vacuum,
stats-gatherer and background writer processes.
  

You will have a process for each database on a separate port.


No - if yours is set up this way, your server is going to be
unnecessarily overloaded. One PostgreSQL postmaster/server process can
run any number of databases on one port. It's only advisable to run more
than one PostgreSQL server process on different ports if you want to run
two different versions of PostgreSQL, or want to dump one set of
databases to a different server (popular during a major version
upgrade.)
  

If all postmaster(s) are running, then perhaps someone or
something(gremlins) :) has modified the pg_hba.conf file in the 
$PGDATA directory?


If the OP can connect to one database on the same server, there's no
reason (aside from data corruption) why he shouldn't be able to connect
to the required one, especially if nothing has changed - he'd get an "no
pg_hba.conf entry for  if the pg_hba.conf file was
mis-configured.

I'd advise the OP to either turn on debug logging in PgAdmin and
re-create the crash, or dump the database from the server, restore as a
different database on the same machine and try to connect to it again.
Matt, if you follow this method, it won't take the database down as long
as you restore the dump to a different database name. If it works, I'd
then advise to dump the original database again, drop it and re-create
it. That will take it down for as long as the dump takes place.

Hope this helps!

Andy.
  

--
--
*From:* Matt Busby [mailto:[EMAIL PROTECTED]
*Sent:* Monday, January 22, 2007 12:10 PM
*To:* Melvin Davidson
*Cc:* pgadmin-support@postgresql.org
*Subject:* RE: [pgadmin-support] Cannot connect to one specific 
postgres database on a server


I can telnet to the database and query the database The site that

is 
  

using the database is also running fine

Not sure what postmast

Re: [pgadmin-support] Positioning the panes

[Andy Shellam (Mailing Lists)]

Hehe yep that's quite funny.
You reminded me that's how I had mine setup in the 1.4 days (I thought 
something looked different!), so I had a go at re-doing, if you haven't 
worked it out:


- Drag the SQL pane out so it's "floating"
- Drag the object explorer pane out so it's "floating", and you have one 
big window with the object properties.
- Drag the SQL pane to the bottom so you have a split-screen and a 
floating object explorer

- Drag the object explorer to the left so it fills the left-side

This is on Windows XP anyway!

Andy.

Laurent Yaish wrote:

Hi,

I can't position the 3 windows panes in the main window like I'd like to.
In 1.4.3 I had the object browser on the left ocuppying 1/3 width and
100% vertical.
The other 2/3 are split vertically between the properties and the SQL 
pane.

Try to drag the panes around and see if you can get them to do that...
It's a real "pain"

Besides that, love the new version!
Thanks,

Laurent

---(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

!DSPAM:37,45b531b2118214216076088!





--
Andy Shellam
NetServe Support Team

the Mail Network
"an alternative in a standardised world"

p: +44 (0) 121 288 0832/0839
m: +44 (0) 7818 000834


---(end of broadcast)---
TIP 3: Have you checked our extensive FAQ?

  http://www.postgresql.org/docs/faq

[pgadmin-support] Issues with roles

[Andy Shellam (Mailing Lists)]

A couple of niggly little issues with the roles in PgAdmin 1.6.2 on an 
8.2.1 server.


When you click Login/Group Roles in the object explorer, you cannot 
right-click and do "new role" like you can with Databases and Tablespaces.
Also the "New object of this type" button is not enabled when you click 
New group/login role - you have to add a new role by right-clicking the 
server connection, New Object... New Group/Login Role.


Any chance of having this sorted for the next release?

Thanks,

--
Andy Shellam
NetServe Support Team

the Mail Network
"an alternative in a standardised world"



---(end of broadcast)---
TIP 3: Have you checked our extensive FAQ?

  http://www.postgresql.org/docs/faq

Re: [pgadmin-support] Issues with roles

[Andy Shellam (Mailing Lists)]

Andy Shellam (Mailing Lists) wrote:
A couple of niggly little issues with the roles in PgAdmin 1.6.2 on an 
8.2.1 server.


When you click Login/Group Roles in the object explorer, you cannot 
right-click and do "new role" like you can with Databases and 
Tablespaces.
Also the "New object of this type" button is not enabled when you 
click New group/login role - you have to add a new role by 
right-clicking the server connection, New Object... New Group/Login Role.


Any chance of having this sorted for the next release?

Thanks,



You also cannot drop a role from PgAdmin as all the Edit menu items are 
greyed out, except Properties.



---(end of broadcast)---
TIP 3: Have you checked our extensive FAQ?

  http://www.postgresql.org/docs/faq

Re: [pgadmin-support] Issues with roles

[Andy Shellam (Mailing Lists)]

Dave Page wrote:

Andy Shellam (Mailing Lists) wrote:

Andy Shellam (Mailing Lists) wrote:
A couple of niggly little issues with the roles in PgAdmin 1.6.2 on 
an 8.2.1 server.


When you click Login/Group Roles in the object explorer, you cannot 
right-click and do "new role" like you can with Databases and 
Tablespaces.
Also the "New object of this type" button is not enabled when you 
click New group/login role - you have to add a new role by 
right-clicking the server connection, New Object... New Group/Login 
Role.


Any chance of having this sorted for the next release?

Thanks,



You also cannot drop a role from PgAdmin as all the Edit menu items 
are greyed out, except Properties.


All works for me. Are you sure the user you are logging in as has 
CREATEROLE privileges?


OK just discovered something weird... you're right in saying the user 
doesn't have 'create role' privelege, however, if I right-click the 
server connection, new object, new role, it works - and the role gets 
created within the server because I can use psql on the server to 
connect with the new role - only snag is once you've added the role in 
PgAdmin, you have to Refresh the login role list manually (right-click 
Refresh.)


Perhaps it's because I have super-user ticked for this user?  If so, 
does that override the CREATE ROLE privelege?


I can send some screenshots showing the  process if needed.

Andy.


---(end of broadcast)---
TIP 4: Have you searched our list archives?

  http://archives.postgresql.org

Re: [pgadmin-support] My SQL pane has gone

[Andy Shellam (Mailing Lists)]

View menu -> Sql Pane??


Ezequias Rodrigues da Rocha wrote:

Hi list,

My sql pane dessapears when I did a drag and drop in some way. Now it 
does not appears anymore.


Any suggestion would be great.

--
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
  Atenciosamente (Sincerely)
Ezequias Rodrigues da Rocha
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
A pior das democracias ainda é melhor do que a melhor das ditaduras
The worst of democracies is still better than the better of dictatorships
http://ezequiasrocha.blogspot.com/ !DSPAM:37,45c73960182622108816872! 


---(end of broadcast)---
TIP 4: Have you searched our list archives?

  http://archives.postgresql.org

Re: [pgadmin-support] My SQL pane has gone

[Andy Shellam (Mailing Lists)]

Ezequias Rodrigues da Rocha wrote:

No way. I was trying this many times but notting of it appears.


It depends where it was when you closed it, when you use the menu option 
it puts it back where it was when it was closed.

Have you got two monitors - could it be beyond the borders of your monitor?

Is it something a remove and re-install can fix?



---(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] My SQL pane has gone

[Andy Shellam (Mailing Lists)]

Dave Page wrote:

Andy Shellam (Mailing Lists) wrote:
  

Ezequias Rodrigues da Rocha wrote:


No way. I was trying this many times but notting of it appears.
  

It depends where it was when you closed it, when you use the menu option
it puts it back where it was when it was closed.
Have you got two monitors - could it be beyond the borders of your monitor?

Is it something a remove and re-install can fix?



No - but the Default View menu option should restore things to default.

Regards, Dave.
  


I thought that would do it, but I closed my SQL pane, then clicked View 
-> Default View, and nothing happened.
Tried dragging the SQL pane somewhere else, clicked View -> Default 
View, nothing happened again.  It still stayed where I'd put it.  This 
is on 1.6.2 on Windows XP.


Andy.

Re: [pgadmin-support] Graphical explain plan sometimes shows "using" for the index name

[Andy Shellam (Mailing Lists)]

Is this still present in the latest version of PgAdmin?  v1.6.2 is the 
current stable version.


Regards,

Andy.


O'Shea, Brendan wrote:

This is a bug in the graphical explain plan in the pgAdmin III Query
tool.  In the graphical explain plan if your query is ordering with the
help of an index and the order is "Descending" then the graphical
explain plan just says "using" as the index name.  If the sort order is
ascending then the correct index name is displayed.  Here are the
relevant lines from the textual output from explain:


DESC
->  Index Scan Backward using idx_name on table_name
ASC
->  Index Scan using idx_name on table_name

This may be because the code for getting the index name is grabbing the
4th word and does not check to see if the word "Backward" was added to
the line, in which case the 5th word should be used.

My Environment:
pgAdmin III 1.4.3
Default config, downloaded precomplied binary for windows
Windows XP
Postgresql 8.1.4


To reproduce the problem is simple, just be sure to order by an indexed
column and then click the Explain Query button:

select * from table_name order by indexed_col  asc limit 1
select * from table_name order by indexed_col desc limit 1


I did a mailing list search but didn't see anyone else reporting this.
If it's a newly found bug then I'd greatly appreciate it if someone
could fix this.  I use the graphical query explain tool a lot, I find it
to be very useful when designing new queries.

Thanks,
Brendan

---(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

!DSPAM:37,45c775e918511302212047!


  


---(end of broadcast)---
TIP 6: explain analyze is your friend

Re: [pgadmin-support] Password Policy

[Andy Shellam (Mailing Lists)]

Clodoaldo wrote:

2007/2/10, Ezequias Rodrigues da Rocha <[EMAIL PROTECTED]>:

Hi list,

Is there any password polity that postgresql implement ?

It is possible to put a set all no administrators passwords to = 
'123456'

from times and times ?

Has anyone implement a dinamic password autentication (the password 
changes

according the date/month etc of a day ) ?


Are you sure you are posting to the correct list? The postgresql
general list is:
http://archives.postgresql.org/pgsql-general/

Regards,


pgsql-admin would also be appropriate to help with this.

Regards
Andy


---(end of broadcast)---
TIP 2: Don't 'kill -9' the postmaster

Re: [pgadmin-support] PgAdmin : table backup problem

[Andy Shellam (Mailing Lists)]

I seem to recall this having cropped up a few weeks ago.  Dave will be 
able to confirm but I think this may have been fixed for 1.6.3?


Regards,

Andy.


Cassiano, Marco wrote:

Hello everybody,
 
I have a problem when I try to backup a table from inside PgAdmin.

If I select a table and choose to backup it, I get the following result :
 
C:\Programmi\pgAdmin III\1.6\pg_dump.exe -i -h pgsvil.manord.com -p 
5432 -U user -F c -v -f "C:\collezioni.backup" -t collezioni -n anamat mdn

pg_dump: server version: 8.2.1; pg_dump version: 8.2.0
pg_dump: proceeding despite version mismatch
pg_dump: No matching tables were found
pg_dump: *** aborted because of error
 
Il processo ha ritornato il codice di uscita 1.
 
The version mismatch is just a warning. Pg_dump tries to continue 
despite of that. (By the way, I have the last version of Pg_Admin 
installed, 1.6.2)
 
The real problem  is the second one : "pg_dump: No matching tables 
were found"
 
If I understand well, PgAdmin fails in composing the correct pg_dump 
command.
The switch combination -t collezioni -n anamat doesn't work. The 
manual says that the -n switch is ignored when -t is used
 
The right (at least, working) syntax seems to be the following :
 
/usr/local/pgsql/bin/pg_dump -U user -F c -v -f /tmp/collezioni.backup 
-t anamat.collezioni mdn
 
That is : I have to prepend the schema to table name in the -t switch.
 
Here is the backup result :


pg_dump: reading schemas
pg_dump: reading user-defined functions
pg_dump: reading user-defined types
pg_dump: reading procedural languages
pg_dump: reading user-defined aggregate functions
pg_dump: reading user-defined operators
pg_dump: reading user-defined operator classes
pg_dump: reading user-defined conversions
pg_dump: reading user-defined tables
pg_dump: reading table inheritance information
pg_dump: reading rewrite rules
pg_dump: reading type casts
pg_dump: finding inheritance relationships
pg_dump: reading column info for interesting tables
pg_dump: finding the columns and types of table "collezioni"
pg_dump: finding default expressions of table "collezioni"
pg_dump: flagging inherited columns in subtables
pg_dump: reading indexes
pg_dump: reading indexes for table "collezioni"
pg_dump: reading constraints
pg_dump: reading foreign key constraints for table "collezioni"
pg_dump: reading triggers
pg_dump: reading triggers for table "collezioni"
pg_dump: reading dependency data
pg_dump: saving encoding = LATIN1
pg_dump: saving standard_conforming_strings = off
pg_dump: dumping contents of table collezioni
I also tried to copy pg_dump.exe from a Postgres 8.2.3 install into 
the PgAdmin directory. The only result has been to eliminate the 
version mismatch problem.
 
Thank you for any advice
 


Marco Cassiano
 
Manifatture del Nord srl unipersonale

Gruppo MaxMara

via Mazzacurati 6
42100 Reggio Emilia RE
ITALY

Tel. +39 0522 358215
Fax +39 0522 268715
email : [EMAIL PROTECTED]
www.pennyblack.com 

 

The contents of the present communication is strictly confidential and 
reserved solely to the referred addressees. In the event was received 
by person different from the addressee, it is forbidden the diffusion, 
distribution and copy. In the event you have received it mistakenly we 
ask you to inform us and to destroy and/or to delete it by your 
computer, without using the data herein contained.


 

The present message (eventual annexes inclusive) shall not be 
considered any contractual proposal and/or acceptance of offer coming 
from the addressee, nor waiver neither recognizance of rights, debts 
and/or credits, and it shall not be binding, when it is not executed a 
subsequent agreement by person who could lawfully represent us. No 
pre-contractual liability shall derive to us, when the present 
communication is not followed by any binding agreement between the 
parties.


---------

 
!DSPAM:37,45d42ea418518608311276! 



--
Andy Shellam
NetServe Support Team

the Mail Network
"an alternative in a standardised world"

p: +44 (0) 121 288 0832/0839
m: +44 (0) 7818 000834

Re: [pgadmin-support] pgadmin3 and fc6

[Andy Shellam (Mailing Lists)]

twenger26 wrote:

I saw a previous post where someone had the same problem as I, but their
solution didn't work for me.  I am trying to install pgadmin3 of FC6 and I
keep getting the error:  "libpq.so.5 is needed by pgadmin3-1.6.1-2.i386".  I
have two versions of postgresql on my system, but I am currently using the
newer version of postgres which contains "libpq.so.5" in
/usr/local/pgsql/lib.  I made sys-links to this file in /usr/lib and
usr/local/lib, but when I try to install it I get the same error.  Is there
some other way to get pgadmin to locate this postgresql library.  
  


Try linking the libpq.so.5 library in /lib as well.
Failing that, edit /etc/ld.so.conf, add "/usr/local/pgsql/lib" to the 
bottom, and run "ldconfig."


Andy

Re: [pgadmin-support] pgAdmin III 1.6.2 sends plaintext password

[Andy Shellam (Mailing Lists)]

patrimith wrote:

Greetings List!

I'm trying get remote management of postrgesql on Ubuntu 5.10 set up.

I am hoping to set up authentication in pg_hba.conf as

host all all 192.168.0.0/0 md5

but I wasn't successful. When I relaxed it to:

host all all 192.168.0.0/0 password

everything worked fine.

Can someone let me know how to configure pgAdmin so that it sends the
password md5 encrypted?

Thanks,

Patrick Smith
http://www.openengagement.com

  


I currently talk to a PostgreSQL 8.2.3 server using PgAdmin 1.6.2 with 
MD5 encrypted passwords just fine.
What is the value of "password_encryption" in your PostgreSQL server's 
postgresql.conf file?


[EMAIL PROTECTED] ~]# cat /endeavour/dbstore/postgresql.conf|grep 
'password_encryption'

password_encryption = on
[EMAIL PROTECTED] ~]#

Try setting it to 'on' and restarting your server.

Regards,

Andy.

Re: [pgadmin-support] pgAdmin III 1.6.2 sends plaintext password

[Andy Shellam (Mailing Lists)]

patrimith wrote:

Andy Shellam (Mailing Lists) wrote:
  
What is the value of "password_encryption" in your PostgreSQL server's 
postgresql.conf file?


[EMAIL PROTECTED] ~]# cat /endeavour/dbstore/postgresql.conf|grep 
'password_encryption'

password_encryption = on
[EMAIL PROTECTED] ~]#




That's the value in my PostgreSQL server's postgresql.conf.

Are you saying that pgAdmin knows the password_encryption setting for the
server?
  


I'm not sure, but I'd hazard a guess it's the underlying libpq library 
that during the handshake works out which authentication scheme to use.
How was your user created?  When you add a new login role, it stores the 
encrypted password in the login profile:


CREATE ROLE test LOGIN ENCRYPTED PASSWORD 
'md505a671c66aefea124cc08b76ea6d30bb'

 NOINHERIT
  VALID UNTIL 'infinity';

If the value of password_encryption was set to off when the user was 
created, I'd guess it would create it with a plain-text password (not 
100% sure.)



I'd like to be able to connect using both plaintext and md5-encrypted
passwords to the same server depending on the environment in which the
client lives.
  


Create a different line in pg_hba.conf for each host environment 
(network IP range), using the relevant "password" or "md5" keyword.


Andy.

Re: [pgadmin-support] pgadmin3 and fc6

[Andy Shellam (Mailing Lists)]

twenger26 wrote:


Andy Shellam (Mailing Lists) wrote:
  

twenger26 wrote:


I saw a previous post where someone had the same problem as I, but their
solution didn't work for me.  I am trying to install pgadmin3 of FC6 and
I
keep getting the error:  "libpq.so.5 is needed by pgadmin3-1.6.1-2.i386". 
I

have two versions of postgresql on my system, but I am currently using
the
newer version of postgres which contains "libpq.so.5" in
/usr/local/pgsql/lib.  I made sys-links to this file in /usr/lib and
usr/local/lib, but when I try to install it I get the same error.  Is
there
some other way to get pgadmin to locate this postgresql library.  
  
  

Try linking the libpq.so.5 library in /lib as well.
Failing that, edit /etc/ld.so.conf, add "/usr/local/pgsql/lib" to the 
bottom, and run "ldconfig."


Andy






Sorry, I meant to say I had it in the /lib directory as well.  I tried
running ldconfig with what you said and it didn't work doing it that way
either.   When I run ld it says:  "/usr/local/pgsql/lib is not a known
library" and the rpm still can't locate the libpq.so.5 file.  

  


Ah sorry I've just re-read your original e-mail and thought you meant 
the error was when you ran PgAdmin, not while trying to install the RPM.


I believe this is because the client libraries weren't installed via the 
RPM package manager (that's the problem I had back when I used Fedora.)


Try doing a "force"'d install - (see rpm --help), I think it's something 
like "rpm --force -i /path/to/pgadmin.rpm".


You may get other libraries, particularly OpenSSL, that also need 
linking to /lib and /usr/lib etc.  That worked for me on FC5 with 
PgAdmin 1.4.3.


HTH

Andy.

Re: [pgadmin-support] pgadmin3 and fc6

[Andy Shellam (Mailing Lists)]

Try --nodeps instead of --force.

Hopefully that should tell it to ignore any package dependencies.

tyson wrote:
I tried using the --force and it still throws the same conflict.  For 
some reason it can't locate that libpq.so.5 link  Not sure what else I 
can do!


Andy Shellam (Mailing Lists) wrote:

twenger26 wrote:

Andy Shellam (Mailing Lists) wrote:
 

twenger26 wrote:
   
I saw a previous post where someone had the same problem as I, but 
their
solution didn't work for me.  I am trying to install pgadmin3 of 
FC6 and

I
keep getting the error:  "libpq.so.5 is needed by 
pgadmin3-1.6.1-2.i386". I
have two versions of postgresql on my system, but I am currently 
using

the
newer version of postgres which contains "libpq.so.5" in
/usr/local/pgsql/lib.  I made sys-links to this file in /usr/lib and
usr/local/lib, but when I try to install it I get the same error.  Is
there
some other way to get pgadmin to locate this postgresql library.  


Try linking the libpq.so.5 library in /lib as well.
Failing that, edit /etc/ld.so.conf, add "/usr/local/pgsql/lib" to 
the bottom, and run "ldconfig."


Andy





Sorry, I meant to say I had it in the /lib directory as well.  I tried
running ldconfig with what you said and it didn't work doing it that 
way

either.   When I run ld it says:  "/usr/local/pgsql/lib is not a known
library" and the rpm still can't locate the libpq.so.5 file. 
  


Ah sorry I've just re-read your original e-mail and thought you meant 
the error was when you ran PgAdmin, not while trying to install the RPM.


I believe this is because the client libraries weren't installed via 
the RPM package manager (that's the problem I had back when I used 
Fedora.)


Try doing a "force"'d install - (see rpm --help), I think it's 
something like "rpm --force -i /path/to/pgadmin.rpm".


You may get other libraries, particularly OpenSSL, that also need 
linking to /lib and /usr/lib etc.  That worked for me on FC5 with 
PgAdmin 1.4.3.


HTH

Andy.





--
Andy Shellam
NetServe Support Team

the Mail Network
"an alternative in a standardised world"

p: +44 (0) 121 288 0832/0839
m: +44 (0) 7818 000834


---(end of broadcast)---
TIP 7: You can help support the PostgreSQL project by donating at

   http://www.postgresql.org/about/donate

[pgadmin-support] Update Guru for Admin Pack

[Andy Shellam (Mailing Lists)]

Hi,

Just a quick request to update the "This server lacks instrumentation 
features" Guru message for PostgreSQL 8.2.
I've just downloaded the source for PgAdmin, looked at the readme in 
"xtra/admin81", and found the instructions in there that PostgreSQL 8.2 
now includes the admin pack as standard.


Can this info be added into the Guru message instead?

PG 8.2:
The admin pack is now part of the core PostgreSQL distribution but is 
not installed by default.
To install, change into the "contrib/adminpack" directory in your 
PostgreSQL 8.2.x source distribution, and make/make install from there.


Thanks

Andy.

[pgadmin-support] Admin pack's "logfile" doesn't work

[Andy Shellam (Mailing Lists)]

Hi,

I have PgAdmin 1.6.2 talking to a PostgreSQL 8.2.3 server with the 
distributed admin pack installed (from source's contrib/adminpack), and 
have ran the adminpack.sql script against the postgres database.  If, in 
PgAdmin, I click Tools > Server Status and select the "logfile" tab, I 
get the following error:


"redirect_stderr not enabled or log_filename misconfigured."

My PostgreSQL server is configured as follows:

silent_mode --- on
log_destination --- stderr
log_directory --- /var/log/pgsql
log_filename --- postgresql.%Y%m%d.log
log_rotation_age --- 1d
redirect_stderr --- on

I've tried it with silent_mode set to "off" and stopped/started 
PostgreSQL, but it still doesn't work.


Is there anything else I need to check/change to get PgAdmin reading the 
log file?  Obviously the log is readable/writeable to the postgresql 
user account, and is around 400KB per day.


Thanks,

Andy.

Re: [pgadmin-support] Chg Pwd Help

[Andy Shellam (Mailing Lists)]

Can you connect to the database to start with?  If you can, then you're 
OK - if not, you need a password (or access to the server's pg_hba.conf 
file.)


To get the password dialogue shown in that website, connect to the 
Postgres server, and on the File menu, click "Change Password."
Or, extend "Logins", right-click the user to change the password for, 
and click Properties - key a new password (twice) and OK, you're good to go.


Andy.

Randy Everette wrote:


Hi:

 

I was hoping you could help me out. I'm brand new to postgres, so 
assume I know nothing.


 

I'm having trouble doing something you'd think is very simple, change 
the postgres password.


 


If you go to this page:

http://www.pgadmin.org/docs/1.6/using.html

It says there is a change pwd dialog, which is displayed on this page:

http://www.pgadmin.org/docs/1.6/password.html

 

HOWEVER, it does not tell you how to get to the password.html page 
within pgadmin. I've tried the web, clicking around in pgadmin, and 
pgadmin help and silly me can't figure it out.


 


Can you help?

 


**r/**

**Randy Everette**

 

 

!DSPAM:37,45d7843c18514886615150! 



--
Andy Shellam
NetServe Support Team

the Mail Network
"an alternative in a standardised world"

p: +44 (0) 121 288 0832/0839
m: +44 (0) 7818 000834

Re: [pgadmin-support] Font size in query windows

[Andy Shellam (Mailing Lists)]

Hi Dan,

Dan Harris wrote:

Hello,

I'm running the latest OS X binary and hoping to replace my existing 
expensive query tool with it.  However, I am having some problems with 
the SQL Query window.  The input window default font is too small, 
almost unreadable ( running 1900x1280 resolution ).  I don't see how 
to increase this font size or change it to a fixed-width font.  I 
tried to go to the preferences pane but the Preferences menu option is 
disabled.  Is this a bug?


Thanks
-Dan

---(end of broadcast)---
TIP 2: Don't 'kill -9' the postmaster

!DSPAM:37,45dc9db518519251411709!




Does the following work for you...

File > Options > Query > Font?

This is how you set it on Windows, not sure if it's the same on OS X.


Regards,

Andy.