Jacob Champion <
jchamp...@timescale.com> escreveu:
> On Wed, Jan 25, 2023 at 7:47 AM Israel Barth Rubio
> wrote:
> > I imagine more people might have already hit a similar situation too.
> While the
> > workaround can seem a bit weird, in my very humble opinion
Hello Jim/Jacob,
> > I do not think it is worth it to change the current behavior of
> PostgreSQL
> > in that sense.
>
> Well, I am not suggesting to change the current behavior of PostgreSQL in
> that matter. Quite the contrary, I find this feature very convenient,
> specially when you need to
Hello Jim,
> Hi Jelte, thanks for the message. You're right, an invalid cert path
> does solve the issue - I even use it for tests. Although it solves the
> authentication issue it still looks in my eyes like a non intuitive
> workaround/hack. Perhaps a new sslmode isn't the right place for this
., 7 de out. de 2022 às 17:54, Israel Barth Rubio <
barthisr...@gmail.com> escreveu:
> Hello Zhihong,
>
> > For the last question, please take a look at:
> >
> > #define MemSetAligned(start, val, len) \
> >
> > which is called by palloc0().
>
> Oh
> Attached is a draft patch along the lines I speculated about above.
> It breaks backwards compatibility in that PreventInTransactionBlock
> commands will now be rejected if they're a non-first command in a
> pipeline. I think that's okay, and arguably desirable, for HEAD
> but I'm pretty
Hello Zhihong,
> For the last question, please take a look at:
>
> #define MemSetAligned(start, val, len) \
>
> which is called by palloc0().
Oh, I totally missed that. Thanks for the heads up!
I'm attaching the new patch version, which contains both the fix
to the problem reported by Andres,
Hello Andres,
> cfbot shows that tests started failing with this version:
>
https://cirrus-ci.com/github/postgresql-cfbot/postgresql/commitfest/39/3822
> A full backtrace is at
https://api.cirrus-ci.com/v1/task/5354378189078528/logs/cores.log
Thanks for pointing this out. I had initially missed
Hello Zhihong,
> + /* attribute is NOT to be copied from input */
>
> I think saying `is NOT copied from input` should suffice.
>
> + /* fieldno is 0-index and attnum is 1-index */
>
> 0-index -> 0-indexed
I have applied both suggestions, thanks! I'll submit a 4th version
Hello Andrew,
> . There needs to be a check that this is being used with COPY FROM, and
> the restriction needs to be stated in the docs and tested for. c.f.
> FORCE NULL.
>
> . There needs to be support for this in psql's tab_complete.c, and
> appropriate tests added
>
> . There needs to be
n writes:
>
> > On 2022-08-16 Tu 14:12, Israel Barth Rubio wrote:
> >> Hello all,
> >>
> >> With the current implementation of COPY FROM in PostgreSQL we are
> >> able to load the DEFAULT value/expression of a column if the column
> >> is absent in the li
Hello,
Thanks for your review. I submitted the patch to the next commit fest
(https://commitfest.postgresql.org/39/3822/).
Regards,
Israel.
Em qua., 17 de ago. de 2022 às 18:56, Andrew Dunstan
escreveu:
>
> On 2022-08-17 We 17:12, Israel Barth Rubio wrote:
> >
> >
> >
t; 2,\\D
>> 3,"\D"
>> \.
COPY 3
postgres=# TABLE copy ;
id | value
+---
1 | \D
2 | \\D
3 | \D
(3 rows)
Does that address your concerns?
I am attaching the new patch, containing the above test in the regress
suite.
Best regards,
Israel.
Em ter., 16 de ago. de
Hello all,
With the current implementation of COPY FROM in PostgreSQL we are able to
load the DEFAULT value/expression of a column if the column is absent in the
list of specified columns. We are not able to explicitly ask that
PostgreSQL uses
the DEFAULT value/expression in a column that is
13 matches
Mail list logo
