hello everyone,
how can i connect to postgres 7.3 using pgadmin3, im using linux 9 redhat.
a message appear while trying to configure the connection
//
An error has accurred
error connecting to the server
fatal: no pg_hba.conf entry for host 127.0.0.1, user postgres
Hi,
I think I found an easier way:
lsof -c postmaster | wc -l
lsof -u postgres | wc -l
Another option is to 'ps wwaux', then grep for postgres PIDS, then use
the 'lsof -p' option and give it a comma-separated list of postgres PIDs.
Cheers
Rudi.
Rudi Starcevic wrote:
Hi,
I'd like to know how ma
Hi,
I'd like to know how many total system files Postgresql has open at any
one time.
Is this the easiest way ??
a) Find out how many Postgres process's - `ps aux | grep postgres`
b) For each Postgres process find out which files it has open - `ls
/proc/*postgres_process_id*/fd | wc -l`
c) Add
Peter Eisentraut <[EMAIL PROTECTED]> writes:
> Tom Lane writes:
>> I'm not sure there's any really good answer to this short of changing
>> the way that users and databases work, which so far no one has wanted
>> to do.
> One possibility would be to have an explicit "flush privileges" command
> th
Tom Lane writes:
> The reason it's difficult is that users span databases; when you drop a
> user in database A, you have no way of seeing/removing references to him
> that exist in databases B, C, ...
>
> I'm not sure there's any really good answer to this short of changing
> the way that users a
Peter Eisentraut <[EMAIL PROTECTED]> writes:
> DHS Webmaster writes:
>> Are there any plans to handle these issues transparently when a user is
>> dropped?
> "Wishlist" maybe, but no concrete plans.
The reason it's difficult is that users span databases; when you drop a
user in database A, you ha
ow writes:
> Can you clarify how this would be better than the second option I described?
> Unless pg_restore can somehow create FK constraints differently (and more
> efficiently) than using "ALTER TABLE xxx ADD CONSTRAINT", I do not see how this
> would help.
If you you pg_dump and dump schema
--- Peter Eisentraut <[EMAIL PROTECTED]> wrote:
> ow writes:
>
> > 1) dump the data only, create the table with all indexes and constraints
> (from
> > script that has nothing to do with pg_restore), import the data. The import
> > part was running for hours (14+) with no end in sight. Had to kil
ow writes:
> 1) dump the data only, create the table with all indexes and constraints (from
> script that has nothing to do with pg_restore), import the data. The import
> part was running for hours (14+) with no end in sight. Had to kill it.
Dump the data and the schema and it will do it in the
Greg Spiegelberg writes:
> Is there a way to "deport" a database on systemA and "import" it on
> systemB without having to do a pg_dump/pg_restore? Basically ask
> the database on systemA to stop using dbA1 under /data/dbA1 then tell
> systemB to use the database already at /data/dbA1.
Not possi
pgSql 7.4.rc2
Hi,
Am somewhat lost about how one should use pg_restore with large dbs. For
simplicity, let's assume that db has only one (1) table with huge amout of
rows. Tried several approaches:
1) dump the data only, create the table with all indexes and constraints (from
script that has not
Hiya,
I have an interesting problem and haven't found an answer yet on
Google.
On systemA we have a LUN from our SAN mounted as /data and one instance
of 7.3.4 with many databases. Each database has it's own PGDATA
directory: /data/dbA1 for dbA1 database. /data/dbA2 for dbA2 and so on.
The defaul
DHS Webmaster writes:
> I noticed this with groups in the past and have become accustomed to
> deleting these users from the groups before dropping them. Otherwise I
> had to create dummy users with those IDs, go about cleaning things out
> and then drop the dummy user.
> Will I have to perform th
I have experienced this in the past with members of groups, but now with
relation ACLs. It goes like this:
Certain users are given specific permissions of different tables and
such.
The users are later dropped but reference to them remains in the ACL as
their former ID number.
When trying to revoke
At 11:49 AM 11/11/2003, Ray Ontko wrote:
>Sounds like an opportunity for someone at Sun to fund a
>little research project. Any Sun/Postgresql hackers out
>there? Any Sun project managers lurking out there?
Does Solaris 8 have the same problem? We run postgres on Solaris 6 with no
problems at
On Wed, 12 Nov 2003, exciteworks hosting wrote:
> Is there an easy way to copy all DBs and users on a server to another
> server?
>
> I need to get an exact duplicate.
pg_dump -h source_server|psql -h dest_server
---(end of broadcast)---
TIP 5:
Hi,
Your query should be written in much simple way:
SELECT Monatsbeitrag.lfdid, Daten.Kundennummer FROM Daten, Monatsbeitrag
WHERE
(Daten.Vetrag widerufen = 2) AND
Daten.ewmanfrdat IS NOTNULL AND
(Monatsbeitrag.ID = Daten.Kundennummer ) AND
((Monatsbeitrag.Monat + 14 ) = '2003-10-27 00
Hello,
sorry for my previos mail.
This was a mistake...
I have an problem with the following statement.
This one works fine and give me the results in just a few seconds.
SELECT Monatsbeitrag.lfdid, Daten.Kundennummer FROM Daten, Monatsbeitrag WHERE
Daten.Vetrag widerufen = 2 ) AND NOT((Dat
ow wrote:
>
> --- Bruce Momjian <[EMAIL PROTECTED]> wrote:
> > You can restrict pg_hba.conf to not allow connections just to one
> > database if you want.
> >
>
> True, but that still would not prevent users who are already connected from
> accessing the db, would it?
No, I guess that is the pr
--
Markus Espenhain Fon: +49 (7 11) 48 90 83 - 0
ETES - EDV-Systemhaus GbRFax: +49 (7 11) 48 90 83 - 50
Libanonstrasse 58 A * D-70184 Stuttgart Web: http://www.etes.de
---(end of broadcast)---
TIP 4: Don't
ow wrote:
>
> --- Bruce Momjian <[EMAIL PROTECTED]> wrote:
> > No, I guess that is the problem. You can use restart, which will kick
> > everyone out, or you can use reload, but that doesn't kick people out of
> > the single database you want.
> >
>
> Restarting the db server triggers the whole
--- Bruce Momjian <[EMAIL PROTECTED]> wrote:
> No, I guess that is the problem. You can use restart, which will kick
> everyone out, or you can use reload, but that doesn't kick people out of
> the single database you want.
>
Restarting the db server triggers the whole chain of events: other db
did you started your database using the -i parameter ?
send-me the startup string you are using.
-
Marco Túlio Oliveira
IT-Manager
www.telecontrol.com.br
- Original Message -
From: "dojie pornea" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Thursday,
--- Bruce Momjian <[EMAIL PROTECTED]> wrote:
> You can restrict pg_hba.conf to not allow connections just to one
> database if you want.
>
True, but that still would not prevent users who are already connected from
accessing the db, would it?
Thanks
__
Do y
Thanks Tom and Reece for replying. It turns out that the
cryptolib/cryptsrc/random source combination I specified --
openssl/system/openssl -- was the problem; changing the combination to
openssl/builtin/openssl, "solved" the problem.
~/contrib/pgcrypto/Makefile snippet:
# either 'builtin', 'mhash
In an attempt to throw the authorities off his trail, [EMAIL PROTECTED] (exciteworks
hosting) transmitted:
> Is there an easy way to copy all DBs and users on a server to another
> server?
>
> I need to get an exact duplicate.
How exact is "exact"?
One notion of "exact" would involve stopping th
ow wrote:
>
> --- Bruce Momjian <[EMAIL PROTECTED]> wrote:
> >
> > Rather than restart the server (kicking everyone out), does 'reload'
> > help to keep new users out and let the old ones leave on their own?
> >
>
> Not really ... users (old or new) should not work with the db unless it's
> com
I already created the database, the services are good
as well as the network connection but still I can't
connect to the Database. I'm using pgAdminII for
win98. The errors I've encountered are listed below:
Could not connect to the server;
Could not connect to remote socket.
Check each of the f
In the last exciting episode, [EMAIL PROTECTED] (Andrew Sullivan) wrote:
> On Tue, Nov 11, 2003 at 01:52:26PM -0700, scott.marlowe wrote:
>>
>> I thought .org and .info were being run on postgresql/solaris?
>
> They are. I'd happily dump the Solaris use overboard, however, if it
> weren't for all
--- Oli Sennhauser <[EMAIL PROTECTED]> wrote:
> What about having two database clusters on a server for separating HA
> from "not so HA" databases? You can take down one db cluster. And people
> can still work on the other one (DB Cluster does nothing has to do with
> hardware or os cluster).
Greetings!
After I upgraded RedHat 9 to Fedora Core 1 my pgAdmin 3 stopped working
with an error message, saying that a library that's no longer used by
Fedora was needed. Fedora has a new version of this library, with a
different name, that pgAdmin isn't able to use.
Is there any new binary
Hello
Not really ... users (old or new) should not work with the db unless it's
completely loaded. Restarting the server will affect activity in other dbs in
that cluster which is not desirable :( IMHO, there should be a way to do this
without restarting the server.
What about having two datab
Hi,
It appears that pgSql can be configured to log the executed statements.
However, the log does not appear to contain any info about who's running the
statement. Any way to change this?
Thanks
__
Do you Yahoo!?
Protect your identity with Yahoo! Mail Addres
--- Bruce Momjian <[EMAIL PROTECTED]> wrote:
>
> Rather than restart the server (kicking everyone out), does 'reload'
> help to keep new users out and let the old ones leave on their own?
>
Not really ... users (old or new) should not work with the db unless it's
completely loaded. Restarting t
34 matches
Mail list logo
