Le dim. 9 juin 2019 à 04:27, Michael Paquier a écrit :
> On Sat, Jun 08, 2019 at 04:23:55PM +0200, Guillaume Lelarge wrote:
> > We might find more typos, but it will take time. Applying this patch now
> > (if it fits you) is probably better.
>
> I can imagine that it is a daunting task... Ok,
On Sat, Jun 08, 2019 at 04:23:55PM +0200, Guillaume Lelarge wrote:
> We might find more typos, but it will take time. Applying this patch now
> (if it fits you) is probably better.
I can imagine that it is a daunting task... Ok, for now I have
applied what you sent. Thanks!
--
Michael
Le sam. 8 juin 2019 à 15:44, Julien Rouhaud a écrit :
> On Sat, Jun 8, 2019 at 3:33 PM Michael Paquier
> wrote:
> >
> > Hi Guillaume,
> >
> > On Wed, May 29, 2019 at 08:28:59PM +0200, Guillaume Lelarge wrote:
> > > Sure.
> >
> > I have noticed your message on the French list about the
On Sat, Jun 8, 2019 at 3:33 PM Michael Paquier wrote:
>
> Hi Guillaume,
>
> On Wed, May 29, 2019 at 08:28:59PM +0200, Guillaume Lelarge wrote:
> > Sure.
>
> I have noticed your message on the French list about the completion of
> the traduction, and congrats for that, it is a huge amount of work.
Hi Guillaume,
On Wed, May 29, 2019 at 08:28:59PM +0200, Guillaume Lelarge wrote:
> Sure.
I have noticed your message on the French list about the completion of
the traduction, and congrats for that, it is a huge amount of work.
Did you find anything else after your last report?
--
Michael
Le mer. 29 mai 2019 19:52, Michael Paquier a écrit :
> On Wed, May 29, 2019 at 07:47:12PM +0200, Guillaume Lelarge wrote:
> > Yeah, I still have quite a lot to process. That might be better to do it
> > all in once.
>
> OK, thanks! Could you ping me on this thread once you think you are
> done?
On Wed, May 29, 2019 at 07:47:12PM +0200, Guillaume Lelarge wrote:
> Yeah, I still have quite a lot to process. That might be better to do it
> all in once.
OK, thanks! Could you ping me on this thread once you think you are
done?
--
Michael
signature.asc
Description: PGP signature
Le mer. 29 mai 2019 19:45, Michael Paquier a écrit :
> On Wed, May 29, 2019 at 05:30:33PM +0200, Guillaume Lelarge wrote:
> > And here is another one. See patch attached.
>
> Are you still going through some parts of the documentation? Perhaps
> you may notice something else? I am wondering if
On Wed, May 29, 2019 at 05:30:33PM +0200, Guillaume Lelarge wrote:
> And here is another one. See patch attached.
Are you still going through some parts of the documentation? Perhaps
you may notice something else? I am wondering if it would be better
to wait a bit more so as we can group all
On Tue, May 28, 2019 at 09:46:48PM +0200, Guillaume Lelarge wrote:
> Hehe, that was the first thing I wrote :) but went with "table and index"
> as it was also used a bit later in the chapter. Both are fine with me.
Okay, done this way. Thanks for the report.
--
Michael
signature.asc
Le mar. 28 mai 2019 à 21:46, Guillaume Lelarge a
écrit :
> Le mar. 28 mai 2019 à 21:28, Michael Paquier a
> écrit :
>
>> On Tue, May 28, 2019 at 05:05:10PM +0200, Guillaume Lelarge wrote:
>> >
>> >> linkend="catalog-pg-am">pg_am
>> > - index access methods
>> > + table
Le mar. 28 mai 2019 à 21:28, Michael Paquier a écrit :
> On Tue, May 28, 2019 at 05:05:10PM +0200, Guillaume Lelarge wrote:
> >
> > linkend="catalog-pg-am">pg_am
> > - index access methods
> > + table and index access methods
> >
>
> Perhaps we could just say
On Tue, May 28, 2019 at 05:05:10PM +0200, Guillaume Lelarge wrote:
>
> linkend="catalog-pg-am">pg_am
> - index access methods
> + table and index access methods
>
Perhaps we could just say "relation" here? That's the term used on
the paragraph describing pg_am.
--
Issue found while translating the v12 manual. I also fixed something that
was missing, as far as I understand it (first fix, the typo is the second
fix).
See patch attached.
Thanks.
--
Guillaume.
diff --git a/doc/src/sgml/catalogs.sgml b/doc/src/sgml/catalogs.sgml
index 4c7e93892a..f81f3d4160
>> I'd move the comma not remove it; and I think "the pg_read_file()" is
>> pretty bad English too. So perhaps
>>
>> Note that granting users the EXECUTE privilege on
>> pg_read_file(), or related functions, allows them
>> the
>> ability to read any file on the server which the
>> It seems there's an extra comma between "related" and "functions". Am I
>> correct?
>
> I'd move the comma not remove it; and I think "the pg_read_file()" is
> pretty bad English too. So perhaps
>
> Note that granting users the EXECUTE privilege on
> pg_read_file(), or related
David Fetter writes:
> Is there a useful distinction to be drawn between the files readable
> by the system user who owns the database and those the database itself
> can read?
Probably not. It's possible to create such a distinction with SELinux
or other security tools, but not in plain Unix,
On Tue, Dec 18, 2018 at 06:16:14PM -0500, Tom Lane wrote:
> Tatsuo Ishii writes:
> > While translating the manual into Japanese, I had a hard time to
> > parse following sentence in func.sgml:
>
> > Note that granting users the EXECUTE privilege on the
> > pg_read_file(), or related,
Tatsuo Ishii writes:
> While translating the manual into Japanese, I had a hard time to
> parse following sentence in func.sgml:
> Note that granting users the EXECUTE privilege on the
> pg_read_file(), or related, functions allows them the
> ability to read any file on the server
While translating the manual into Japanese, I had a hard time to
parse following sentence in func.sgml:
Note that granting users the EXECUTE privilege on the
pg_read_file(), or related, functions allows them the
ability to read any file on the server which the database can read and
20 matches
Mail list logo
