On Wed, Aug 26, 2020 at 07:19:09PM -0400, Tom Lane wrote:
> With one eye on the PDF width issue, I propose that we not draw
> the distinction, but just list all the relevant operators for each
> opclass (its native ones, plus the applicable "loose" operators).
> Then we only need two columns, opcla
On Tue, Aug 25, 2020 at 03:27:33PM -0400, Bruce Momjian wrote:
> On Tue, Aug 25, 2020 at 03:10:44PM -0400, Tom Lane wrote:
> > Bruce Momjian writes:
> > > We are inconsistently about adding a comma after e.g. and i.e.:
> >
> > > This summarizes the recommended behavior:
> > > https://jakubmaria
Alvaro Herrera writes:
> On 2020-Aug-26, Bruce Momjian wrote:
>> Stupid question, but do we think the average Postgres user can
>> understand this issue. I am having trouble myself.
> The only reason I think it's worth pointing out, is that the opclass
> name is something you can use in CREATE I
On Wed, Aug 26, 2020 at 01:59:42PM +, PG Doc comments form wrote:
> The following documentation comment has been logged on the website:
>
> Page: https://www.postgresql.org/docs/12/xfunc-c.html
> Description:
>
> In "Table 35-1. Equivalent C Types for Built-in SQL Types", when SQL type is
> "
On 2020-Aug-26, Bruce Momjian wrote:
> On Wed, Aug 26, 2020 at 05:58:01PM -0400, Alvaro Herrera wrote:
> > Well, there is a small problem here ... which is that I misled you with
> > \dAo ... because that one lists the operators for the opfamilies, not
> > for the opclasses. And you can't use the
On Wed, Aug 26, 2020 at 05:58:01PM -0400, Alvaro Herrera wrote:
> Well, there is a small problem here ... which is that I misled you with
> \dAo ... because that one lists the operators for the opfamilies, not
> for the opclasses. And you can't use the opfamily name in CREATE INDEX:
>
> 55432 14d
Alvaro Herrera writes:
> On 2020-Aug-26, Michael Paquier wrote:
>> I would imagine that rowsep=0 for a given can do that:
>> https://tdg.docbook.org/tdg/4.5/entry.html
>> However, it does not make a difference if I use the default style or
>> the website style. I may be missing something with th
On 2020-Aug-26, Michael Paquier wrote:
> On Tue, Aug 25, 2020 at 06:17:28PM -0400, Tom Lane wrote:
> > I wonder if it would look better if we suppress the horizontal rules
> > between the operator names within a cell. IIRC, it's possible to do
> > that, though the exact incantation isn't coming
The following documentation comment has been logged on the website:
Page: https://www.postgresql.org/docs/12/xfunc-c.html
Description:
In "Table 35-1. Equivalent C Types for Built-in SQL Types", when SQL type is
"timestamp", the C type is reported to be "Timestamp * ", whereas it is
actually "Tim
> 26 Aug 2020, в 09:24, Николай Чадаев написал(а):
>
> Thank You Oleg.
>
> A simple example is extremely important and necessary.
> I will wait for this example.
It's already exists. The idea was to add cross links to this.
10 matches
Mail list logo
