On 19/04/18 00:45, Craig Ringer wrote:
I guarantee you that when you create a 100GB EBS volume on AWS EC2,
you don't get 100GB of storage preallocated. AWS are probably pretty
good about not running out of backing store, though.
Some db folks (used to anyway) advise dd'ing to your freshly a
On 22/03/19 3:05 PM, Tom Lane wrote:
> Michael Paquier writes:
>> I would be curious to hear the reason why such tool names have been
>> chosen from the start. The tools have been switched to C in 9e0ab71
>> from 2003, have been introduced by Peter Eisentraut as of 240e4c9 from
>> 1999, and I can
On 9/04/19 12:27 PM, Ashwin Agrawal wrote:
Heikki and I have been hacking recently for few weeks to implement
in-core columnar storage for PostgreSQL. Here's the design and initial
implementation of Zedstore, compressed in-core columnar storage (table
access method). Attaching the patch and link
On 11/04/19 4:01 PM, Mark Kirkwood wrote:
On 9/04/19 12:27 PM, Ashwin Agrawal wrote:
Heikki and I have been hacking recently for few weeks to implement
in-core columnar storage for PostgreSQL. Here's the design and initial
implementation of Zedstore, compressed in-core columnar st
On 23/05/19 12:07 PM, Ashwin Agrawal wrote:
We (Heikki, me and Melanie) are continuing to build Zedstore. Wish to
share the recent additions and modifications. Attaching a patch
with the latest code. Link to github branch [1] to follow
along. The approach we have been leaning towards is to bui
On 20/02/18 13:27, Tsunakawa, Takayuki wrote:
Hello,
I propose changing the default value of wal_sync_method from fdatasync to
open_datasync on Linux. The patch is attached. I'm feeling this may be
controversial, so I'd like to hear your opinions.
The reason for change is better performanc
On 02/03/18 16:53, Alvaro Herrera wrote:
I think it was impolite to post this on the very same day the commitfest
started. We have enough patches as it is ...
To be fair - he did say things like "wanting feedback..." and "shows an
example of using pluggable storage.." and for PG 12. If he h
On 03/03/18 05:03, Robert Haas wrote:
On Fri, Mar 2, 2018 at 5:35 AM, Alexander Korotkov
wrote:
I would propose "zero-bloat heap" disambiguation of zheap. Seems like fair
enough explanation for me without need to rename :)
It will be possible to bloat a zheap table in certain usage patterns
On 26/02/19 4:53 PM, Robert Haas wrote:
On Mon, Feb 25, 2019 at 4:38 PM David Steele wrote:
FWIW, if you weren't selling backrest quite so hard everywhere backups
are mentioned, I'd find this thread a lot more convicing.
pgBackRest has not used exclusive backups since the new API was
introdu
On 26/02/19 5:41 PM, Stephen Frost wrote:
Greetings Mark,
* Mark Kirkwood (mark.kirkw...@catalyst.net.nz) wrote:
ISTM that the onus should be on the patch submitter to provide additions to
pg_basebackup that make it as painless as possible for those people *not*
using pgBackRest to continue
On 27/04/18 19:10, Yuriy Zhuravlev wrote:
1. You can remove tools/msvc folder because all your build rules will
be universal. (cmake build now have much fewer lines of code)
2. You can forget about terminal in Windows (for windows guys it's
important)
3. You can normally check environment on
On 04/12/17 16:08, Ashutosh Bapat wrote:
On Sun, Dec 3, 2017 at 5:56 AM, legrand legrand
wrote:
Hello,
I have a typical star schema, having dimension tables "product", "calendar"
and "country" and a fact table "sales".
This fact table is partitionned by time (range by month) and country (list
On 04/12/17 17:20, Mark Kirkwood wrote:
On 04/12/17 16:08, Ashutosh Bapat wrote:
On Sun, Dec 3, 2017 at 5:56 AM, legrand legrand
wrote:
Hello,
I have a typical star schema, having dimension tables "product",
"calendar"
and "country" and a fact tab
On 15/09/18 08:17, Tom Lane wrote:
Yeah, this. The PG community is mostly nice people, AFAICT. I'll be
astonished (and worried) if the CoC committee finds much to do. We're
implementing this mostly to make newcomers to the project feel that
it's a safe space.
Agreed. However I think the a
14 matches
Mail list logo