Small doc tweak for array/string functions

Hi On these pages: - https://www.postgresql.org/docs/current/functions-array.html - https://www.postgresql.org/docs/current/functions-string.html we point out via "See also" the existence of aggregate array and string functions, but I think it would be useful to also mention the existence of

Minor comment fix for pg_config_manual.h

Hi Attached is mainly to fix a comment in $subject which has a typo in the referenced initdb option ("--walsegsize", should be "--wal-segsize"), and while I'm there also adds a couple of "the" for readability. Regards Ian Barwick -- Ian Barwick

Re: Performance issue in foreign-key-aware join estimation

On Sat, 22 Dec 2018 at 10:53, David Rowley wrote: > Back in [1], I mentioned that I'd like to start moving away from our > linked list based implementation of List and start using an array > based version instead. If we had this we could easily further improve > this code fkey matching code to

Re: Function to track shmem reinit time

On Tue, Apr 10, 2018 at 8:58 PM Robert Haas wrote: > On Tue, Apr 10, 2018 at 9:07 AM, David Steele wrote: > > On 3/29/18 9:40 AM, Tomas Vondra wrote: > >> On 03/28/2018 08:55 PM, David Steele wrote: > >>> I'm setting this entry to Waiting on Author, but based on the discussion > >>> I think it

Re: reducing the footprint of ScanKeyword (was Re: Large writable variables)

On 12/22/18, Tom Lane wrote: > John Naylor writes: >> Using a single file also gave me another idea: Take value and category >> out of ScanKeyword, and replace them with an index into another array >> containing those, which will only be accessed in the event of a hit. >> That would shrink

Re: Joins on TID

Hi, Writing as someone who used TID joins and group by's in the past. One use case is having a chance to peek into what will DELETE do. A lot of GIS tables don't have any notion of ID, and dirty datasets tend to have many duplicates you need to cross-reference with something else. So, you write

Re: [PATCH] Improve tab completion for CREATE TABLE

Michael Paquier writes: > On Sat, Dec 22, 2018 at 01:33:23PM +, Dagfinn Ilmari Mannsåker wrote: >> The CREATE and ALTER TABLE documentation calls them storage parameters, >> so I've gone for table_storage_parameters in the attached v2 patch. > > Sold. And committed. Thanks again! - ilmari

Re: Speeding up text_position_next with multibyte encodings

On 12/23/18 1:26 AM, Heikki Linnakangas wrote: > On 14/12/2018 20:20, John Naylor wrote: >> I signed up to be a reviewer, and I will be busy next month, so I went >> ahead and fixed the typo in the patch that broke assert-enabled >> builds. While at it, I standardized on the spelling

Re: CF app feature request

On Tue, Nov 20, 2018 at 7:19 PM Tom Lane wrote: > Magnus Hagander writes: > > I'm trying to figure out where this thread left off :) My understanding > of > > the consensus is we don't actually want/need a change in the app, but are > > instead OK with the admin just handling it a somewhat ugly

Re: CF app feature request

On Wed, Nov 21, 2018 at 12:52 AM Michael Paquier wrote: > On Tue, Nov 20, 2018 at 03:30:38PM -0300, Alvaro Herrera wrote: > > On 2018-Nov-20, Tom Lane wrote: > > Certainly not higher than having the dropdown for entry author/reviewer > > be sorted alphabetically ... *wink* *wink* > > More *wink*

Re: pgsql: Update ssl test certificates and keys

On Tue, Nov 27, 2018 at 02:21:39PM +, Peter Eisentraut wrote: > Update ssl test certificates and keys > > Debian testing and newer now require that RSA and DHE keys are at > least 2048 bit long and no longer allow SHA-1 for signatures in > certificates. This is currently causing the ssl