Postgres Pro
Downloads
Home   >   mailing lists

Re: make MaxBackends available in _PG_init - Mailing list pgsql-hackers

From Greg Sabino Mullane
Subject Re: make MaxBackends available in _PG_init
Date
Msg-id CAKAnmmJ_3HQZ7PvpiJoJKYfffp8GOUXE3BVHsD9EOjDrcrU1FA@mail.gmail.com
Whole thread Raw
In response to Re: make MaxBackends available in _PG_init  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses RE: make MaxBackends available in _PG_init  ("wangsh.fnst@fujitsu.com" <wangsh.fnst@fujitsu.com>)
List pgsql-hackers
Tree view
On Wed, Aug 11, 2021 at 10:08 AM Tom Lane <tgl@sss.pgh.pa.us> wrote:
You must not have enabled EXEC_BACKEND properly.  It's a compile-time
#define that affects multiple modules, so it's easy to get wrong.
The way I usually turn it on is

Thank you. I was able to get it all working, and withdraw any objections to that bit of the patch. :)

Cheers,
Greg
 

pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Expanding regexp_matches flags
Next
From: Greg Sabino Mullane
Date:
Subject: Re: Add option --drop-cascade for pg_dump/restore