Hi, I have installed (tnx to everyone) postres 6.5. Now I must to wrap the
port 6542 so no one extern to my machine can telnet the postgres DB.
Any help or any RTFM?
Le uniche cose che girano sotto Windows 95 sono le palle.
--
Michel ZioBudda Morelli [EMAIL PROTECTED]
On Thu, 8 Jul 1999, Oleg Broytmann wrote:
On Thu, 8 Jul 1999, ZioBudda wrote:
Hi, I have installed (tnx to everyone) postres 6.5. Now I must to wrap the
port 6542 so no one extern to my machine can telnet the postgres DB.
Any help or any RTFM?
Run Postgres with TCP/IP disabled
On Thu, 8 Jul 1999, ZioBudda wrote:
Hi, I have installed (tnx to everyone) postres 6.5. Now I must to wrap the
port 6542 so no one extern to my machine can telnet the postgres DB.
Any help or any RTFM?
Run Postgres with TCP/IP disabled (remove -i from start-up options) and
use UNIX sockets
On Thu, 8 Jul 1999, ZioBudda wrote:
On Thu, 8 Jul 1999, Oleg Broytmann wrote:
Run Postgres with TCP/IP disabled (remove -i from start-up options) and
use UNIX sockets to connect to postgres (you don't need anything special -
libpq knows how to handle this situation).
I have tried
On Thu, 8 Jul 1999, Oleg Broytmann wrote:
Run Postgres with TCP/IP disabled (remove -i from start-up options).
Ok, but I must to integrated postgres with PHP3. If I remove -i php3 does
not works.
Pensa alla vita: usa le cinture di sicurezza.
--
Michel ZioBudda Morelli [EMAIL
On Thu, 8 Jul 1999, ZioBudda wrote:
On Thu, 8 Jul 1999, Oleg Broytmann wrote:
Run Postgres with TCP/IP disabled (remove -i from start-up options).
Ok, but I must to integrated postgres with PHP3. If I remove -i php3 does
not works.
There is no way. Either disable TCP/IP or use HBA.
Oleg Broytmann wrote:
There is no way. Either disable TCP/IP or use HBA. When using TCP/IP + HBA,
Postgres will listen on its TCP/IP port, and telnetting is always possible.
HBA helps to restrict access to databases, but not to TCP/IP port.
You can try to configure firewall on you
ok, the company (www.mpsllc.com) is now completely on postgres with
primarily access97 front-end (we are working on some perl/cgi scripts to
interact w/ the database over an intranet also) -- 20 users. i have
reported hanging up problems to this group, but those haven't recurred
since we
JT Kirkpatrick wrote:
1) we have a second hd in the system that can be used as a backup device,
in addition to a tape. i had planned to simply copy the directory via a
tar command run through cron. is that the best way, or should i consider a
pg_dump (which i know nearly nothing about)?
Lamar Owen wrote:
[snip]
2) how do i schedule a regular vacuum through cron? do you not have to be
in psql to do a vacuum? or can you do it from the bash prompt? (we are
using linux rh 5.2, kernel 2.2.2, postgres 6.4.2)
Again, my crontab (sub your database name for "intranet"):
Hi, I have installed (tnx to everyone) postres 6.5. Now I must to wrap the
port 6542 so no one extern to my machine can telnet the postgres DB.
Any help or any RTFM?
5432, you mean. If you don't use -i flag to postmaster, it will never
listen on any tcp/ip port. It uses only unix domain
Now, I updated the database installation to the last 6.5 release,
hoping that it would fixed the bugs but no. The same thing
happen except now that other query to the used-to-be-locked table
now complete (thanks to the new MVCC!) Also it is now pg_temp.X
files which are eating all the
On 8 Jul, Lamar Owen wrote:
Try the following one-liner (yes, one liner. e-mail will break it up,
and the syntax is kindof picky -- xargs is a great tool, even if it is a
little farkled):
psql -t -c "select datname from pg_database" template1|xargs -n 1 psql
-q -c "vacuum analyze"
13 matches
Mail list logo
