On 06/10/2016 10:20 AM, David G. Johnston wrote:
Can you be more precise? A single table can only be placed onto one
file system.
Only if those different file systems have different physical
characteristics is using a tablespace likely to be a good solution. In
other scenarios having some kin
On Fri, Jun 10, 2016 at 1:12 PM, Rakesh Kumar
wrote:
> > Their main problem to overcome when using them is that they tie
> PostgreSQL
> > much more tightly to the underlying configuration of the operating system
> > and thus you need to ensure that your processes and procedures
> accommodate
> >
> Their main problem to overcome when using them is that they tie PostgreSQL
> much more tightly to the underlying configuration of the operating system
> and thus you need to ensure that your processes and procedures accommodate
> that reality since the tools that PostgreSQL provides can only do s
On Fri, Jun 10, 2016 at 12:26 PM, Rakesh Kumar
wrote:
> I saw a slide recently where the use of tablespaces was discouraged.
> What does the community think of tablespaces.
>
They are a tool and their use should neither be encouraged nor discouraged
but rather understood and used when appropriat
I saw a slide recently where the use of tablespaces was discouraged.
What does the community think of tablespaces.
thanks
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
