On 5/21/13 2:41 PM, Bruce Momjian wrote:
I have thought about this and there are potentially several options
specified to pg_upgrade that could be passed into scripts:
-O, --new-options=OPTIONS new cluster options to pass to the server
-P, --new-port=NEWPORTnew cluster port
On Wed, May 29, 2013 at 09:42:12AM -0400, Peter Eisentraut wrote:
On 5/21/13 2:41 PM, Bruce Momjian wrote:
I have thought about this and there are potentially several options
specified to pg_upgrade that could be passed into scripts:
-O, --new-options=OPTIONS new cluster options to
On May 21, 2013, at 2:41 PM, Bruce Momjian wrote:
On Wed, May 8, 2013 at 08:52:40PM -0400, Bruce Momjian wrote:
On Wed, May 8, 2013 at 05:05:05PM -0400, Ray Stell wrote:
A minor detail in 9.2.4, but I noticed that the pg_upgrade flag for
superuser, -u, does not get carried to a -U flag on
On Wed, May 8, 2013 at 08:52:40PM -0400, Bruce Momjian wrote:
On Wed, May 8, 2013 at 05:05:05PM -0400, Ray Stell wrote:
A minor detail in 9.2.4, but I noticed that the pg_upgrade flag for
superuser, -u, does not get carried to a -U flag on the vacuumdb commands
written to
A minor detail in 9.2.4, but I noticed that the pg_upgrade flag for
superuser, -u, does not get carried to a -U flag on the vacuumdb commands
written to analyze_new_cluster.sh.
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
On Wed, May 8, 2013 at 05:05:05PM -0400, Ray Stell wrote:
A minor detail in 9.2.4, but I noticed that the pg_upgrade flag for
superuser, -u, does not get carried to a -U flag on the vacuumdb commands
written to analyze_new_cluster.sh.
OK, let me look at this issue.
--
Bruce Momjian
