On 30 June 2017 06:45:04 EEST, Noah Misch wrote:
>This PostgreSQL 10 open item is past due for your status update.
>Kindly send
>a status update within 24 hours, and include a date for your subsequent
>status
>update.
I'll fix this some time next week. (I'm on vacation right now)
- Heikki
On Sun, Jun 25, 2017 at 09:26:28PM -0700, Noah Misch wrote:
> On Fri, Jun 23, 2017 at 10:23:36AM +0900, Michael Paquier wrote:
> > On Fri, Jun 23, 2017 at 3:02 AM, Heikki Linnakangas wrote:
> > > I'm inclined to change gen_random_uuid() to throw an error if the server
> > > is
> > > built with --
Hi,
On Thu, Jun 29, 2017 at 9:23 PM, wrote:
> The following documentation comment has been logged on the website:
>
> Page: https://www.postgresql.org/docs/9.1/static/libpq-pgpass.html
> Description:
>
> Can we keep encrypted password in .pgpass file or is there any way to
> provide encrypted pa
The following documentation comment has been logged on the website:
Page: https://www.postgresql.org/docs/9.1/static/libpq-pgpass.html
Description:
Can we keep encrypted password in .pgpass file or is there any way to
provide encrypted password to connect to postgres or can we pass password to
ps
The following documentation comment has been logged on the website:
Page: https://www.postgresql.org/docs/9.6/static/ddl-rowsecurity.html
Description:
The policy documentation page is great, and the example in it is very
informative, but I just discovered a major flaw in our implementation of it