On Mon, May 17, 2021 at 08:07:02PM +, PG Doc comments form wrote:
> The Solution.pm file has the following lines:
> if ($self->{options}->{gss})
> {
> $proj->AddIncludeDir($self->{options}->{gss} . '\inc\krb5');
> $proj->AddLibrary($self->{options}->{gss} .
>
On 2021/05/17 20:46, Fujii Masao wrote:
>
>
> On 2021/05/17 18:58, Masahiro Ikeda wrote:
>>
>>
>> On 2021/05/17 15:32, Fujii Masao wrote:
>>>
>>>
>>> On 2021/05/14 17:00, Masahiro Ikeda wrote:
Hi,
I worried the difference between "tup_returned" and "tup_fetched" in
HAVING is another stop-word.
Original Message
On 17 May 2021, 16:43, PG Doc comments form wrote:
> The following documentation comment has been logged on the website:
>
> Page: https://www.postgresql.org/docs/13/functions-comparison.html
> Description:
>
> Hi,
> Just an FYI,
The following documentation comment has been logged on the website:
Page: https://www.postgresql.org/docs/13/install-windows-full.html
Description:
The Solution.pm file has the following lines:
if ($self->{options}->{gss})
{
On Sun, Apr 4, 2021 at 9:53 AM Anton Voloshin wrote:
>
> Hello,
>
> Existing Postgres documentation states in doc/src/sgml/charset.sgml:
> The https://ssl.icu-project.org/icu-bin/locexp;>ICU Locale
> Explorer can be used to check the details of a particular locale
> definition.
>
> But the link
t...@sss.pgh.pa.us wrote:
> Bryn wrote:
>
>> It’s easy to guess values for, say, countries in Europe:
>
> On Unix-ish systems, "locale -a" should provide the set of available values.
> We don't attempt to document this because it's so installation-dependent.
>
>> But what do I use for, say,
Bryn Llewellyn writes:
> It’s easy to guess values for, say, countries in Europe:
On Unix-ish systems, "locale -a" should provide the set of
available values. We don't attempt to document this
because it's so installation-dependent.
> But what do I use for, say, Simplified Chinese?
Maybe you
It’s easy to guess values for, say, countries in Europe:
This:
create function to_char_demo()
returns table(z text)
language plpgsql
as $body$
declare
-- Counted from midnight 1-Jan-1970 UTC.
secs constant double precision not null := 94996756799.456789;
t constant timestamp
The following documentation comment has been logged on the website:
Page: https://www.postgresql.org/docs/13/functions-comparison.html
Description:
Hi,
Just an FYI, but I'm running into a somewhat annoying issue with the
documentation search that I'm not sure you're aware of.
Namely, searching
On 2021/05/17 18:58, Masahiro Ikeda wrote:
On 2021/05/17 15:32, Fujii Masao wrote:
On 2021/05/14 17:00, Masahiro Ikeda wrote:
Hi,
I worried the difference between "tup_returned" and "tup_fetched" in
pg_stat_database. I assumed that "tup_returned" means the number of tuples
that
Hi
Attached a patch to delete "CURRENT(as of 2020) " description in POSIX Time
Zone Specifications.
I'm not a native English speaker, if my fix is not appropriate or insufficient,
please be kind to share your thought with me.
Regards,
Tang
On 2021/05/17 15:32, Fujii Masao wrote:
>
>
> On 2021/05/14 17:00, Masahiro Ikeda wrote:
>> Hi,
>>
>> I worried the difference between "tup_returned" and "tup_fetched" in
>> pg_stat_database. I assumed that "tup_returned" means the number of tuples
>> that returned to clients. Of course, this
On 2021/05/14 17:00, Masahiro Ikeda wrote:
Hi,
I worried the difference between "tup_returned" and "tup_fetched" in
pg_stat_database. I assumed that "tup_returned" means the number of tuples
that returned to clients. Of course, this is wrong.
- Number of rows returned by queries in
13 matches
Mail list logo
