Campbell, Lance написа:
PostgreSQL: 8.2.4
OS: Linux Red Hat 4.x 64 bit
I have a database running on serverA with postgres user userA. I want
to migrate the database to ServerB with a postgres user userB. Notice
the users are not the same. I did the following to put the database on
Could someone clarify the database dump/restore requirement for postgres
upgrades between major releases?
The online help chapter 23.5. Migration Between Releases states that:
As a general rule, the internal data storage format is subject to change
between major releases of PostgreSQL (where
George Wilk написа:
Could someone clarify the database dump/restore requirement for postgres
upgrades between major releases?
The online help chapter 23.5. Migration Between Releases states that:
As a general rule, the internal data storage format is subject to change
between major
Am Mittwoch, 15. August 2007 16:20 schrieb George Wilk:
I thought that the major release was the first number in the versioning
schema, the second represented minor release, and the third would be the
maintenance release or revision number (i.e. 8.2.4).
You thought wrong then.
--
Peter
Hi Peter, thanks for your helpful and kind reply. It certainly clears a lot
of smoke... In the future you might consider including links to relevant
information.
-Original Message-
From: Peter Eisentraut [mailto:[EMAIL PROTECTED]
Sent: Wednesday, August 15, 2007 10:44 AM
To:
Am Mittwoch, 15. August 2007 16:52 schrieb George Wilk:
Hi Peter, thanks for your helpful and kind reply. It certainly clears a
lot of smoke... In the future you might consider including links to
relevant information.
You posted the relevant information yourself. You just need to believe
This must be a matter of personal pride for you Peter, as your personal
website states: I spend much of my spare time programming, writing
documentation for, and answering mailing list questions about PostgreSQL.
Whereas answering mailing list questions might be an understatement :)
I'll let you
George Wilk wrote:
As a general rule, the internal data storage format is subject to change
between major releases of PostgreSQL (where the number after the first dot
changes). This does not apply to different minor releases under the same
major release (where the number after the second dot
On Wed, Aug 08, 2007 at 06:35:51PM -0300, Anderson Alves de Albuquerque wrote:
After user $USER execute this ALTER, it get change PASSWORD. Could I block
command ALTER password to user $USER?
No, there's no way to do that. You might want to look at using
ident-based authentication for that
On 8/15/07, George Wilk [EMAIL PROTECTED] wrote:
From: Peter Eisentraut [mailto:[EMAIL PROTECTED]
Sent: Wednesday, August 15, 2007 10:44 AM
To: pgsql-admin@postgresql.org
Cc: George Wilk
Subject: Re: [ADMIN] Migration Between Releases
Am Mittwoch, 15. August 2007 16:20 schrieb George Wilk:
Hi Alexander,
Use 0.0.0.0/0. You can of course add multiple lines to match all your
ranges (e.g. 192.168.0.0/24, 10.0.0.0/8 etc.)
Regards,
Andy.
Alexander B. wrote:
Hi people,
I would like to configure pg_hba for any IP.
I have several network mask, some times 192..., or 10, or
Hi people,
I would like to configure pg_hba for any IP.
I have several network mask, some times 192..., or 10, or 190
..., ... ...
How can I configure for any IP?
Thanks
Alexander
---(end of broadcast)---
TIP 9: In versions below 8.0,
A few notes. postgres looks through pg_hba.conf until it finds the
*first* entry that matches and tries to authenticate and connect using
that method. There's no fallback, so order of entries is important.
If you just want to have any IP connect using one particular
authentication method, put
Hi,
I am looking for some suggestions to optimize the following
problem/solution.
Given two nodes A and B (two computers) in a active-passive mode where A is
running PG engine, and B is simply standing by, and a common storage
(twin tailed) ( or from pg_ctl point of view -D /common/data ), I
[ADMIN] unsubcribe
---(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
Hi folks!
That's another sob sob.. I can't connect to socket blah blah ..
.s.PGSQL.5432 asking for help. But this is somewhat bizarre, and i'm not
used to the 8.2's postgresql.conf file.
I'm running a PostgreSQL 8.4.2 powered by Debian Sarge (very)Unstable. My
PHP application successfully
El mié, 15-08-2007 a las 17:13 -0300, Hilton Perantunes escribió:
Hi folks!
That's another sob sob.. I can't connect to socket blah
blah .. .s.PGSQL.5432 asking for help. But this is somewhat bizarre,
and i'm not used to the 8.2's postgresql.conf file.
I'm running a PostgreSQL 8.4.2
Thanks for answering, Julio.
When I stop the database, the socket file is automatically removed. That's
the way it happened before... but now, oddly enough, I restarted the
database at will several times, my app is still running, pgadmin too... and
no socket file is created. o.0
(and I still
Hilton Perantunes [EMAIL PROTECTED] writes:
When I stop the database, the socket file is automatically removed. That's
the way it happened before... but now, oddly enough, I restarted the
database at will several times, my app is still running, pgadmin too... and
no socket file is created. o.0
El mié, 15-08-2007 a las 13:39 -0500, Peter Koczan escribió:
A few notes. postgres looks through pg_hba.conf until it finds the
*first* entry that matches and tries to authenticate and connect using
that method. There's no fallback, so order of entries is important.
If you just want to have
Hi,
If i start the service in service panel the following error is occurs.
Could not start the PostgreSQL Scheduling Agent - pgAgent service on
Local Computer.
Error 1053: The service did not respond to the start or control request
in a timely fashion.
Kindly give me
21 matches
Mail list logo
