On 09/01/2015 08:46 PM, Andy Colson wrote:
On 09/01/2015 07:00 PM, Bruce Momjian wrote:
On Tue, Sep 1, 2015 at 06:56:11PM -0500, Andy Colson wrote:
I also added a mention that rsync, not pg_upgrade, will be run on the
standbys. You can see all the results of the patch here:
http://momjia
On 09/01/2015 07:00 PM, Bruce Momjian wrote:
On Tue, Sep 1, 2015 at 06:56:11PM -0500, Andy Colson wrote:
I also added a mention that rsync, not pg_upgrade, will be run on the
standbys. You can see all the results of the patch here:
http://momjian.us/pgsql_docs/pgupgrade.html
Thanks.
On Tue, Sep 1, 2015 at 06:56:11PM -0500, Andy Colson wrote:
> >I also added a mention that rsync, not pg_upgrade, will be run on the
> >standbys. You can see all the results of the patch here:
> >
> > http://momjian.us/pgsql_docs/pgupgrade.html
> >
> >Thanks.
> >
>
> Sweet, I'm glad I stoppe
On 09/01/2015 04:09 PM, Bruce Momjian wrote:
On Sun, Aug 23, 2015 at 09:45:50AM -0500, Andy Colson wrote:
I think we should add a step 6.5 (before step 7 Stop both servers) with
something like:
If you are upgrading both a primary and standby, then we need to make sure the
standby is caught up
Try this:
SELECT *
FROM information_schema.columns
WHERE UPPER(column_default) LIKE 'NEXTVAL%'
ORDER BY 1, 2, 3;
On Tue, Sep 1, 2015 at 6:33 PM, Tom Lane wrote:
> "FarjadFarid\(ChkNet\)" writes:
> > Can someone please direct me as how to detect columns (serial) with
> > autoincrement optio
"FarjadFarid\(ChkNet\)" writes:
> Can someone please direct me as how to detect columns (serial) with
> autoincrement option ?
They have a default that depends on a nextval() call.
regards, tom lane
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
Hi all,
Can someone please direct me as how to detect columns (serial) with
autoincrement option ?
Many thanks.
Best Regards
Farjad Farid
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-
On Sun, Aug 23, 2015 at 09:45:50AM -0500, Andy Colson wrote:
> I think we should add a step 6.5 (before step 7 Stop both servers) with
> something like:
>
> If you are upgrading both a primary and standby, then we need to make sure
> the standby is caught up.
> If you are wal shipping then on pr
Craig,
By an existing database, I mean I have a database that has our data on it.
I have created the btree_gist and bdr extensions and ran the
bdr.bdr_group_create () function and the bdr.bdr_node_join_wait_for_ready(),
all run successfully. After setting up the next BDR node, and after running
I have not used the bdr_init_copy procedure because I've haven't been able to
find any step by step documentation on how to use. Can you provide some?
--
View this message in context:
http://postgresql.nabble.com/BDR-setup-bdr-node-join-wait-for-ready-tp5863606p5864210.html
Sent from the Pos
10 matches
Mail list logo