Re: Drop type "smgr"?

From: Shawn Debnath <sdn(at)amazon(dot)com>
To: Thomas Munro <thomas(dot)munro(at)gmail(dot)com>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Drop type "smgr"?
Date: 2019-02-28 21:41:45
Message-ID: 20190228214145.GA62457@f01898859afd.ant.amazon.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Fri, Mar 01, 2019 at 10:33:06AM +1300, Thomas Munro wrote:

> It doesn't make any sense to put things like clog or any other SLRU in
> a non-default tablespace though. It's perfectly OK if not all smgr
> implementations know how to deal with tablespaces, and the SLRU
> support should just not support that.

If the generic storage manager, or whatever we end up calling it, ends
up being generic enough - its possible that tablespace value would have
to be respected.

--
Shawn Debnath
Amazon Web Services (AWS)

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Peter Moser 2019-02-28 21:43:41 Re: [HACKERS] [PROPOSAL] Temporal query processing with range types
Previous Message Thomas Munro 2019-02-28 21:33:06 Re: Drop type "smgr"?