Re: Compressed TOAST Slicing
Rafia Sabih <rafia.sabih@enterprisedb.com>
From: Rafia Sabih <rafia.sabih@enterprisedb.com>
To: pramsey@cleverelephant.ca
Cc: Tom Lane <tgl@sss.pgh.pa.us>, sfrost@snowman.net, pgsql-hackers@lists.postgresql.org
Date: 2018-12-02T15:03:03Z
Lists: pgsql-hackers
Commits
Same data as JSON:
GET /api/v1/messages/:b64id/commits
the thread's linked commits as JSON, with link sources.
API reference →
-
Add support for partial TOAST decompression
- 4d0e994eed83 12.0 landed
-
Remove remaining hard-wired OID references in the initial catalog data.
- 3aa0395d4ed3 12.0 cited
-
Rephrase references to "time qualification".
- ebcc7bf949ba 12.0 cited
On Fri, Nov 2, 2018 at 11:55 PM Paul Ramsey <pramsey@cleverelephant.ca> wrote: > > As threatened, I have also added a patch to left() to also use sliced access. Hi Paul, The idea looks good and believing your performance evaluation it seems like a practical one too. I had a look at this patch and here are my initial comments, 1. - if (dp != destend || sp != srcend) + if (!is_slice && (dp != destend || sp != srcend)) return -1; A comment explaining how this check differs for is_slice case would be helpful. 2. - int len = VARSIZE_ANY_EXHDR(str); - int n = PG_GETARG_INT32(1); - int rlen; + int n = PG_GETARG_INT32(1); Looks like PG indentation is not followed here for n. -- Regards, Rafia Sabih EnterpriseDB: http://www.enterprisedb.com/