On Tue, 20 Aug 2019 19:19:01 +0900
Michael Paquier wrote:
> On Tue, Aug 20, 2019 at 03:38:28PM +0900, Takuma Hoshiai wrote:
> > I have attached a patch. The word of "Express" existed in four
> > places, they will are fixed by this patch.
>
> - These compilers can be either from Visual
>
On 8/19/19 10:36 PM, Erik Rijkers wrote:
On 2019-08-20 07:05, Michael Paquier wrote:
On Mon, Aug 19, 2019 at 04:00:13PM -0700, Joshua D. Drake wrote:
New version attached with spelling errors fixed.
I have gone through this patch, and I have a hard time understanding
why these are
PG Doc comments form writes:
> Therefore, in my opinion, the below paragraph should be amended as below.
> * Before
> -
> ANALYZE requires only a read lock on the target table, so it can run in
> parallel with other activity on the table.
> -
> * After
> -
> ANALYZE requires only a
On Tue, Aug 20, 2019 at 03:38:28PM +0900, Takuma Hoshiai wrote:
> I have attached a patch. The word of "Express" existed in four
> places, they will are fixed by this patch.
- These compilers can be either from Visual Studio,
- Visual Studio Express or some versions of the
- Microsoft Windows
The following documentation comment has been logged on the website:
Page: https://www.postgresql.org/docs/11/spi-spi-finish.html
Description:
Hi,
The documentation of SPI_finish clarifies that aborting with elog will
cleanup SPI automatically without need to call to SPI_finish manually, see
The following documentation comment has been logged on the website:
Page: https://www.postgresql.org/docs/9.5/sql-select.html
Description:
The below document says that the ANALYZE statement requires a read lock.
https://www.postgresql.org/docs/current/sql-analyze.html
-
ANALYZE requires only
On Tue, 20 Aug 2019 14:37:09 +0900
Michael Paquier wrote:
> On Tue, Aug 20, 2019 at 02:20:04PM +0900, Takuma Hoshiai wrote:
> > OK, I will send a patch to this thread,right?
>
> If you can send it here, that would be great.
> --
> Michael
I have attached a patch. The word of "Express" existed
