| From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
|---|---|
| To: | pepevo <pepevo(at)yahoo(dot)com> |
| Cc: | Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com>, "cgerard999(at)gmail(dot)com" <cgerard999(at)gmail(dot)com>, Christopher Browne <cbbrowne(at)gmail(dot)com>, Pgsql-admin <pgsql-admin(at)postgresql(dot)org>, Pgsql-general <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: create batch script to import into postgres tables |
| Date: | 2020-06-20 01:38:14 |
| Message-ID: | CAKFQuwbSBCFKJuGjcX6G2+ueP9XGtwdSYaq5DQJbmQA6O1gePQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin pgsql-general |
On Friday, June 19, 2020, pepevo <pepevo(at)yahoo(dot)com> wrote:
> But everything can run by script on the server, right?
>
Separation of concerns. The server with the database cluster should
probably not be running application code. Application code can be run
other machine, “admin” machine is one label. Though for development it
shouldn’t matter so long as the application is configurable. Configure it
for local during development and when in production it pulls production
configuration.
David J.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Adrian Klaver | 2020-06-20 04:10:30 | Re: create batch script to import into postgres tables |
| Previous Message | David G. Johnston | 2020-06-20 00:24:09 | Re: create batch script to import into postgres tables |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Praveen Kumar K S | 2020-06-20 03:15:09 | [HELP] Query regarding logical replication slot |
| Previous Message | David G. Johnston | 2020-06-20 00:24:09 | Re: create batch script to import into postgres tables |