On Sat, Jul 29, 2017 at 1:17 PM, Melvin Davidson <melvin6...@gmail.com> wrote:
> > On Sat, Jul 29, 2017 at 3:38 PM, tel medola <tel.med...@gmail.com> wrote: > >> Depends. >> When you create your tables in new schema, the script was the same from >> "qa"? >> Sequences, tables, etc.. belong to the schema where was created. >> >> Roberto. >> >> Em sáb, 29 de jul de 2017 às 16:17, marcelo <marcelo.nico...@gmail.com> >> escreveu: >> >>> Some days ago I asked regarding tables located in different schemas. >>> Now, my question is >>> Suppose I have two schemas (other than public): "qa" and "production". >>> Initially I create all my tables in "qa". All of them have a primary key >>> of type serial. >>> Later, I will copy the tables definitions to production. >>> It will automatically create the sequences in the new schema, starting >>> at zero? >>> TIA >>> Marcelo >>> >>> >>> -- >>> Sent via pgsql-general mailing list (pgsql-general@postgresql.org) >>> To make changes to your subscription: >>> http://www.postgresql.org/mailpref/pgsql-general >>> >> > > > > > *Marcelo,>Initially I create all my tables in "qa". All of them have a > primary key of type serial. >Later, I will copy the tables definitions to > production.* > > *A word of caution, creating tables in a qa "schema" and then transferring > to production is not the normal/correct (or safe) way to do development.* > > *The standard procedure is to create a seperate "qa" database (and/or > server) with the exact same schema(s) as production. Then, after testing * > > *is completed, the schemas/tables are copied to production.* > > This. Staging should look as much like production as possible for testing purposes. If you HAVE to use the same server (not a good idea) then make separate clusters. Separate servers here can save you a LOT of heartache from someone fat fingering a script meant for staging hitting production.
