| From: | Bruce Momjian <bruce(at)momjian(dot)us> |
|---|---|
| To: | Andreas Joseph Krogh <andreas(at)visena(dot)com> |
| Cc: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: pg_upgrade not able to cope with pg_largeobject being in a different tablespace |
| Date: | 2016-10-19 17:42:50 |
| Message-ID: | 20161019174250.GA1607@momjian.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Thu, Oct 13, 2016 at 04:35:35PM +0200, Andreas Joseph Krogh wrote:
> På torsdag 13. oktober 2016 kl. 16:09:34, skrev Bruce Momjian <bruce(at)momjian(dot)us
> >:
>
> On Thu, Oct 13, 2016 at 10:14:08AM +0200, Andreas Joseph Krogh wrote:
> > I would assume that having pg_largeobject in a separate tablespace is
> more and
> > more common these days, having real-cheap SAN vs. fast-SSD for normal
> tables/
> > indexes/wal.
>
> So common that no one has ever asked for this feature before?
>
> Sometimes one gets the feeling that one is the only one in the universe doing
> something one considers "quite common":-)
Yes, I often feel the same way. :-) Like, why am I the only person who
thinks this is a natural thing to do. I find a lot of bugs that way. :-)
--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com
+ As you are, so once was I. As I am, so you will be. +
+ Ancient Roman grave inscription +
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Greg Sabino Mullane | 2016-10-19 18:03:39 | Re: pg_sample |
| Previous Message | Edilmar LISTAS | 2016-10-19 16:43:13 | Re: Problem changing default data_directory in PG 9.6 + CentOS6 |