Re: [HACKERS] Runtime Partition Pruning

Hello Robert, On Sat, Dec 2, 2017 at 12:34 AM, Robert Haas wrote: > On Fri, Dec 1, 2017 at 6:20 AM, Beena Emerson wrote: >> David Q1: >> postgres=# explain analyse execute ab_q1 (3,3); --const >>

Re: explain analyze output with parallel workers - question about meaning of information for explain.depesz.com

On Wed, Nov 29, 2017 at 2:04 PM, Amit Kapila wrote: > On Tue, Nov 28, 2017 at 9:42 PM, Robert Haas wrote: >> On Tue, Nov 28, 2017 at 2:23 AM, Amit Kapila wrote: >>> That is wrong and I think you have hit a bug. It should

Re: [HACKERS] Custom compression methods

On 12/01/2017 10:52 PM, Andres Freund wrote: > On 2017-12-01 16:14:58 -0500, Robert Haas wrote: >> Honestly, if we can give everybody a 4% space reduction by >> switching to lz4, I think that's totally worth doing -- but let's >> not make people choose it, let's make it the default going forward,

Re: Partition pruning for Star Schema

Hi, On 2017-12-02 13:56:51 -0700, legrand legrand wrote: > 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). You've posted nearly the same a few

Re: [HACKERS] Custom compression methods

On 12/02/2017 09:24 PM, konstantin knizhnik wrote: > > On Dec 2, 2017, at 6:04 PM, Tomas Vondra wrote: > >> On 12/01/2017 10:52 PM, Andres Freund wrote: >> ... >> >> Other algorithms (e.g. zstd) got significantly better compression (25%) >> compared to pglz, but in exchange for longer

Re: Partition pruning for Star Schema

Sorry, I apologize. I though (most) Hackers were not reading General list. Regards PAscal -- Sent from: http://www.postgresql-archive.org/PostgreSQL-hackers-f1928748.html

Re: [HACKERS] Custom compression methods

On 12/02/2017 09:38 PM, Andres Freund wrote: > Hi, > > On 2017-12-02 16:04:52 +0100, Tomas Vondra wrote: >> Firstly, it's going to be quite hard (or perhaps impossible) to find an >> algorithm that is "universally better" than pglz. Some algorithms do >> work better for text documents, some for

Re: [HACKERS] Proposal: Local indexes for partitioned table

David Rowley wrote: > So, then this patch is only really intended as a syntax shortcut for > mass adding of indexes to each partition? This patch is intended to serve as a basis on which to construct further features, just like every other patch we apply. > I feel like we could do better here

Re: [HACKERS] Custom compression methods

Tomas Vondra wrote: > On 12/01/2017 08:48 PM, Alvaro Herrera wrote: > > Maybe our dependency code needs to be extended in order to support this. > > I think the current logic would drop the column if you were to do "DROP > > COMPRESSION .. CASCADE", but I'm not sure we'd see that as a feature. >

pg_dumpall -r -c try to drop user postgres

Hi I am not sure if user postgres should be removed, so it is probably bug pg_dumpall -r -c | grep postgres DROP ROLE postgres; CREATE ROLE postgres; Regards Pavel

Re:Re: [HACKERS] [PATCH]make pg_rewind to not copy useless WAL files

At 2017-12-01 12:27:09, "Michael Paquier" wrote: >On Tue, Oct 3, 2017 at 1:20 AM, chenhj wrote: >> I had filled the authors field of this patch in commitfest, and will rebase >> this patch if needed. Thank you for your help! > >The documentation of

Re: [HACKERS] Custom compression methods

Hi, On 2017-12-02 16:04:52 +0100, Tomas Vondra wrote: > Firstly, it's going to be quite hard (or perhaps impossible) to find an > algorithm that is "universally better" than pglz. Some algorithms do > work better for text documents, some for binary blobs, etc. I don't > think there's a win-win

Re: [HACKERS] Parallel Hash take II

On 2017-12-02 15:54:29 +1300, Thomas Munro wrote: > On Sat, Dec 2, 2017 at 1:55 PM, Andres Freund wrote: > > - Right now RemovePgTempFilesInDir() will recurse into appropriately > > named directories, and when it recurses it doesn't require the same > > name pattern