On 2/28/25 09:26, Krishnakant Mane wrote:
On 2/28/25 22:53, Ron Johnson wrote:
Differing search_path values can lead to problems like this.
So what can I do to resolve this?
In psql do:
\dx
That will show you what extensions are installed and in what schema.
Then read this:
https://www
On 3/2/25 19:44, me nefcanto wrote:
Thank you all for responding. With respect, I don't understand why COPY
gets related to ETL. All of the requirements I mentioned above have
nothing to do with ETL. We have a table of categories. A hierarchical
table. This is a multitenant app. Hundreds of tho
me nefcanto writes:
> The point is, that there is already an `on_error ignore` clause there. This
> means that somewhere there is a try/catch per row. If I'm wrong, please let
> me know.
You are wrong. See
https://git.postgresql.org/gitweb/?p=postgresql.git&a=commitdiff&h=d9f7f5d32
https://git
> On Mar 2, 2025, at 19:44, me nefcanto wrote:
>
> As I have specified in the bug thread, from 11 RDBMSs, 7 support this. Thus
> it's not an uncommon weird request.
If your organization is interested in producing a design and a patch, or paying
a developer or organization to do so, that wou
Thank you all for responding. With respect, I don't understand why COPY
gets related to ETL. All of the requirements I mentioned above have nothing
to do with ETL. We have a table of categories. A hierarchical table. This
is a multitenant app. Hundreds of thousands of records are in it. We want
to
Differing search_path values can lead to problems like this.
On Fri, Feb 28, 2025 at 12:01 PM Krishnakant Mane
wrote:
> Ok here you go.
>
> select create_immv('plantskillpayment', 'select distinct kwapp_plant.id
> as plantid, kwapp_skill.id as skillid, kwapp_skill.skillname,
> kwapp_plant.plantn
