On Fri, Apr 2, 2021 at 11:05 AM Bruce Momjian wrote:
> On Thu, Apr 1, 2021 at 09:46:58PM -0700, Bryn Llewellyn wrote:
> > Or am I misunderstanding something?
> >
> > Try this. The result of each “select” is shown as the trailing comment
> on the
> > same line. I added whitespace by hand to line
On Sun, Apr 15, 2018 at 10:39 AM, David Arnold wrote:
> >More specifically, JSON logging does seem to be a solution in search of a
> problem. PostgreSQL's CSV logs are very easy to machine-parse, and if
> there are corrupt lines being emitted there, the first step should be to
> fix those, rathe
On Sun, Apr 15, 2018 at 11:08 AM, David Arnold wrote:
> >This would appear to solve multiline issues within Fluent.
> >https://docs.fluentd.org/v0.12/articles/parser_multiline
>
> I definitely looked at that, but what guarantees do I have that the
> sequence is always ERROR/STATEMENT/DETAIL?
;{bar}', info->'foo'), info)
I can totally respect the person that slams into this wall the first time
and is REALLY upset about it - but by their own admission this has occurred
multiple times in this project and they continue to not take standard
precautions.
Again, I applaud the patience of many people on this list. You deserve much
more respect than you are being shown here right now.
John W Higgins
On Sun, Nov 24, 2019 at 8:12 AM Ranier Vilela
wrote:
> Hi,
> The test "if (zeropadlen > 0)" is redundant and can be salely removed.
> It has already been tested in the same path.
>
> Best regards,
> Ranier Vilela
>
> --- \dll\postgresql\a\port\snprintf.c 2019-11-23 13:19:20.0 -0300
> ++
ingle
letters (numTables to nTables)
Random places switch from lower case names to upper case names (sentPtr to
WalSentPtr) most places leave lower case names (days to ndays).
Please at least be consistent within the patch itself.
John W Higgins
you do not seem to be approaching
these issues with the correct mindset at the moment. Volume is not the
winner over quality here.
John W Higgins
>
Could I please ask a couple of questions?
Why does the first answer to everything seem to be "we need to destroy
something to make it better for others"? Why does createdb need to be
removed? Why do we use the "newbie that can't understand whether or not
createdb is for PostgreSQL or MySQL or
On Tue, Jul 27, 2021 at 3:36 PM Bryn Llewellyn wrote:
>
> with
> c1 as (
> select
> '1 month 1 day 1 second'::interval as i1,
> '1.234 month 1.234 day 1.234 second'::interval as i3),
>
> c2 as (
> select i1*1.234 as i2, i3 from c1)
>
> select i2::text as i2_txt, i3::text f
On Wed, Jul 28, 2021 at 12:42 AM Dean Rasheed
wrote:
> On Wed, 28 Jul 2021 at 00:08, John W Higgins wrote:
> >
> > It's nice to envision all forms of fancy calculations. But the fact is
> that
> >
> > '1.5 month'::interval * 2 != '3 month":
On Wed, Oct 7, 2020 at 6:35 PM Michael Paquier wrote:
> On Wed, Oct 07, 2020 at 02:31:54PM +0300, Maksim Kita wrote:
> > Fix progname memory leak in ecpg client.
> > Issue taken from todo list https://wiki.postgresql.org/wiki/Todo.
>
> FWIW, I don't see much point in doing that.
>
I hope that ev
11 matches
Mail list logo