| From: | Josh Berkus <josh(at)agliodbs(dot)com> |
|---|---|
| To: | Rajashree Mandaogane <rajashree(dot)28m(at)gmail(dot)com>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Proposal to join the hackers list |
| Date: | 2014-03-13 17:05:57 |
| Message-ID: | 5321E575.3000009@agliodbs.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 03/13/2014 08:54 AM, Rajashree Mandaogane wrote:
> We have decided to modify the storage of PostgresSQL for columnar storage
> along with row based tuple storage. We are trying to modify the planner and
> optimiser to generate the plan using data stored in both both row and
> columnar storage. We are thinking to extend this project after curriculum
> and will integrate btrfs file system with PostgresSQL to store columnar
> data.
Huh? btrfs? Why would anything on the filesystem later be involved?
And why would you tie a PostgreSQL storage backend to a specific filesystem?
--
Josh Berkus
PostgreSQL Experts Inc.
http://pgexperts.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Josh Berkus | 2014-03-13 17:10:00 | Re: 9a57858f1103b89a5674f0d50c5fe1f756411df6 |
| Previous Message | Josh Berkus | 2014-03-13 17:03:42 | Re: Replication slots and footguns |