Hi Greg,
thanks for your suggestions. See below for my comments.
Greg Stark wrote:
Well there isn't a way to do step 2 in one shot either.
Maybe my explanation was not clear. Step2 means run the DDL/DMLscript to
create and populate all the tables.
You'll have to
issue a CREATE statement for
Hi All,
I have some questions for you about the best way to handle permission on
a database in a production system.
The final goal is to have a web application connected to the db using a
single user that must run select/delete/insert/update (and maybe truncate)
In my opinion that user should
I'll run a java webapp running in tomcat connected to postgres via jdbc.
BTW, why the access method should be important ?
I mean, my main question is should pg_xlog be located on a
different EBS than data ?
My doubt is really about logical vs physical disk, since i think EBS is
logical a
wondering if also on ec2 with EBS disks having
pg_xlog on a different EBS disk could be useful.
Thanks in advance
ste
Stefano Nichele wrote:
Do you think that it could useful mounting two different EBS to handle
data and pg_xlog ?
cheers,
ste
--
Sent via pgsql-general mailing list (pgsql
Do you think that it could useful mounting two different EBS to handle
data and pg_xlog ?
cheers,
ste
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
