Re: After the last update

2024-01-15 Thread Adrian Klaver 

On 1/15/24 17:59, Arbol One wrote:

Bro., is in the OP.


1) I am not your Bro.

2) When troubleshooting explicit is better then implicit. What is 
obvious to you might not be obvious others. I have more then once 
assumed and not verified and gone down a long trail of troubleshooting 
only to find the solution became clear only when the assumptions where 
verified or not.


3) You still have not answered if there where errors and if so what they 
are?


4) In conclusion, the sum total of your issue statement is something 
worked now it doesn't. That will not get an answer other then yes you 
have a problem.




-

I am working on an application using NB-20,
PG-psql (16.1 (Debian 16.1-1.pgdg120+1), server 15.5 (Debian 
15.5-1.pgdg120+1)),

postgresql-42.7.0.jar.
openjdk 17.0.9 2023-10-17
OpenJDK Runtime Environment (build 17.0.9+9-Debian-1deb12u1)
OpenJDK 64-Bit Server VM (build 17.0.9+9-Debian-1deb12u1, mixed mode, 
sharing)

and, yes... Debian 12.

For some reason NB is not longer able to interact with PG since the last 
PG package update from Debian.

Is anyone else experiencing the same problem, or is it just me; I wonder.

The question is, how can I tackle this issue.

Thanks in advance.

---

On 2024-01-15 6:22 p.m., Adrian Klaver wrote:

On 1/15/24 14:38, Arbol One wrote:

Netbeans 20. Sorry, my bad.


And the rest of the questions?



On 2024-01-15 4:48 p.m., Adrian Klaver wrote:

On 1/15/24 13:33, Arbol One wrote:

I am working on an application using NB-20,
PG-psql (16.1 (Debian 16.1-1.pgdg120+1), server 15.5 (Debian 
15.5-1.pgdg120+1)),

postgresql-42.7.0.jar.
openjdk 17.0.9 2023-10-17
OpenJDK Runtime Environment (build 17.0.9+9-Debian-1deb12u1)
OpenJDK 64-Bit Server VM (build 17.0.9+9-Debian-1deb12u1, mixed 
mode, sharing)

and, yes... Debian 12.

Fo.r some reason NB is not longer able to interact with PG since the 
last


Define NB.

Error messages are?


PG package update from Debian.


Update from what to what?

Is anyone else experiencing the same problem, or is it just me; I 
wonder.


The question is, how can I tackle this issue.

Thanks in advance.







--
Adrian Klaver
adrian.kla...@aklaver.com

Re: After the last update

2024-01-15 Thread David G. Johnston 
On Mon, Jan 15, 2024 at 2:33 PM Arbol One  wrote:

> I am working on an application using NB-20,
> PG-psql (16.1 (Debian 16.1-1.pgdg120+1), server 15.5 (Debian
> 15.5-1.pgdg120+1)),
> postgresql-42.7.0.jar.
> openjdk 17.0.9 2023-10-17
> OpenJDK Runtime Environment (build 17.0.9+9-Debian-1deb12u1)
> OpenJDK 64-Bit Server VM (build 17.0.9+9-Debian-1deb12u1, mixed mode,
> sharing)
> and, yes... Debian 12.
>
> For some reason NB is not longer able to interact with PG since the last
> PG package update from Debian.
> Is anyone else experiencing the same problem, or is it just me; I wonder.
>
> The question is, how can I tackle this issue.
>

If you want good help you need to be much more specific and detailed in the
information you provide.  Beyond that, debugging is a skill that basically
boils down to trying things, figuring out where the problem originates.
Usually with the help of error messages.  Does psql work?  Is the
server even running?  I do wonder whether the fact your psql is reporting
v16 but the server is v15 is a meaningful symptom.  Again, finding the
error message usually is the most useful first step.  Otherwise you need to
be extra wordy in describing exactly what you are doing and seeing that you
believe is a problem. "not longer able to interact" is an insufficient
description.

I've not yet seen anyone else complain of issues on these mailing lists;
though if the problem is with NetBeans and v16 maybe they report them to a
more appropriate NB oriented place?

David J.

Re: After the last update

2024-01-15 Thread Arbol One 

Bro., is in the OP.

-

I am working on an application using NB-20,
PG-psql (16.1 (Debian 16.1-1.pgdg120+1), server 15.5 (Debian 
15.5-1.pgdg120+1)),

postgresql-42.7.0.jar.
openjdk 17.0.9 2023-10-17
OpenJDK Runtime Environment (build 17.0.9+9-Debian-1deb12u1)
OpenJDK 64-Bit Server VM (build 17.0.9+9-Debian-1deb12u1, mixed mode, 
sharing)

and, yes... Debian 12.

For some reason NB is not longer able to interact with PG since the last 
PG package update from Debian.

Is anyone else experiencing the same problem, or is it just me; I wonder.

The question is, how can I tackle this issue.

Thanks in advance.

---

On 2024-01-15 6:22 p.m., Adrian Klaver wrote:

On 1/15/24 14:38, Arbol One wrote:

Netbeans 20. Sorry, my bad.


And the rest of the questions?



On 2024-01-15 4:48 p.m., Adrian Klaver wrote:

On 1/15/24 13:33, Arbol One wrote:

I am working on an application using NB-20,
PG-psql (16.1 (Debian 16.1-1.pgdg120+1), server 15.5 (Debian 
15.5-1.pgdg120+1)),

postgresql-42.7.0.jar.
openjdk 17.0.9 2023-10-17
OpenJDK Runtime Environment (build 17.0.9+9-Debian-1deb12u1)
OpenJDK 64-Bit Server VM (build 17.0.9+9-Debian-1deb12u1, mixed 
mode, sharing)

and, yes... Debian 12.

For some reason NB is not longer able to interact with PG since the 
last


Define NB.

Error messages are?


PG package update from Debian.


Update from what to what?

Is anyone else experiencing the same problem, or is it just me; I 
wonder.


The question is, how can I tackle this issue.

Thanks in advance.






--
ArbolOne.ca
Using Fire Fox and Thunderbird.
ArbolOne is composed of students and volunteers dedicated to providing free 
services to charitable organizations.
ArbolOne on Java Development is in progress [ í ]

Re: After the last update

2024-01-15 Thread Adrian Klaver 

On 1/15/24 14:38, Arbol One wrote:

Netbeans 20. Sorry, my bad.


And the rest of the questions?



On 2024-01-15 4:48 p.m., Adrian Klaver wrote:

On 1/15/24 13:33, Arbol One wrote:

I am working on an application using NB-20,
PG-psql (16.1 (Debian 16.1-1.pgdg120+1), server 15.5 (Debian 
15.5-1.pgdg120+1)),

postgresql-42.7.0.jar.
openjdk 17.0.9 2023-10-17
OpenJDK Runtime Environment (build 17.0.9+9-Debian-1deb12u1)
OpenJDK 64-Bit Server VM (build 17.0.9+9-Debian-1deb12u1, mixed mode, 
sharing)

and, yes... Debian 12.

For some reason NB is not longer able to interact with PG since the last


Define NB.

Error messages are?


PG package update from Debian.


Update from what to what?

Is anyone else experiencing the same problem, or is it just me; I 
wonder.


The question is, how can I tackle this issue.

Thanks in advance.





--
Adrian Klaver
adrian.kla...@aklaver.com

Re: After the last update

2024-01-15 Thread Arbol One 

Netbeans 20. Sorry, my bad.

On 2024-01-15 4:48 p.m., Adrian Klaver wrote:

On 1/15/24 13:33, Arbol One wrote:

I am working on an application using NB-20,
PG-psql (16.1 (Debian 16.1-1.pgdg120+1), server 15.5 (Debian 
15.5-1.pgdg120+1)),

postgresql-42.7.0.jar.
openjdk 17.0.9 2023-10-17
OpenJDK Runtime Environment (build 17.0.9+9-Debian-1deb12u1)
OpenJDK 64-Bit Server VM (build 17.0.9+9-Debian-1deb12u1, mixed mode, 
sharing)

and, yes... Debian 12.

For some reason NB is not longer able to interact with PG since the last


Define NB.

Error messages are?


PG package update from Debian.


Update from what to what?

Is anyone else experiencing the same problem, or is it just me; I 
wonder.


The question is, how can I tackle this issue.

Thanks in advance.




--
ArbolOne.ca
Using Fire Fox and Thunderbird.
ArbolOne is composed of students and volunteers dedicated to providing free 
services to charitable organizations.
ArbolOne on Java Development is in progress [ í ]

Re: After the last update

2024-01-15 Thread Adrian Klaver 

On 1/15/24 13:33, Arbol One wrote:

I am working on an application using NB-20,
PG-psql (16.1 (Debian 16.1-1.pgdg120+1), server 15.5 (Debian 
15.5-1.pgdg120+1)),

postgresql-42.7.0.jar.
openjdk 17.0.9 2023-10-17
OpenJDK Runtime Environment (build 17.0.9+9-Debian-1deb12u1)
OpenJDK 64-Bit Server VM (build 17.0.9+9-Debian-1deb12u1, mixed mode, 
sharing)

and, yes... Debian 12.

For some reason NB is not longer able to interact with PG since the last


Define NB.

Error messages are?


PG package update from Debian.


Update from what to what?


Is anyone else experiencing the same problem, or is it just me; I wonder.

The question is, how can I tackle this issue.

Thanks in advance.



--
Adrian Klaver
adrian.kla...@aklaver.com

After the last update

2024-01-15 Thread Arbol One 

I am working on an application using NB-20,
PG-psql (16.1 (Debian 16.1-1.pgdg120+1), server 15.5 (Debian 
15.5-1.pgdg120+1)),

postgresql-42.7.0.jar.
openjdk 17.0.9 2023-10-17
OpenJDK Runtime Environment (build 17.0.9+9-Debian-1deb12u1)
OpenJDK 64-Bit Server VM (build 17.0.9+9-Debian-1deb12u1, mixed mode, 
sharing)

and, yes... Debian 12.

For some reason NB is not longer able to interact with PG since the last 
PG package update from Debian.

Is anyone else experiencing the same problem, or is it just me; I wonder.

The question is, how can I tackle this issue.

Thanks in advance.

--
ArbolOne.ca
Using Fire Fox and Thunderbird.
ArbolOne is composed of students and volunteers dedicated to providing free 
services to charitable organizations.
ArbolOne on Java Development is in progress [ í ]

Re: Help with "Create Extension unaccent"

2024-01-15 Thread Adrian Klaver 

On 1/15/24 12:04, Lan Xu wrote:

Hi Adrian and Ian,

Thank you for responding!

OS: CentOS 7.9.2009
Postgres: 14.5

It was an upgrade from an older version.


From what repo?

And was that same repo as the older version was installed from?



Thanks again! Thank you for your guidance!

Lan


On Jan 14, 2024, at 8:50 AM, Adrian Klaver  wrote:

On 1/13/24 21:52, Lan Xu wrote:

With CREATE EXTENSION unaccent, I’m getting the following:
ERROR:  extension "unaccent" has no installation script nor update path for version 
“1.0"
But I can find it under /usr/share/pgsql/extension/unaccent001.0.sql
Thank you for your help!


What OS and version?

What Postgres version?

How did you install Postgres?


Lan


--
Adrian Klaver
adrian.kla...@aklaver.com





--
Adrian Klaver
adrian.kla...@aklaver.com

Re: Moving to Postgresql database

2024-01-15 Thread Henrique Lima 
You can find a lot information in this link

https://docs.aws.amazon.com/dms/latest/oracle-to-aurora-postgresql-migration-playbook/chap-oracle-aurora-pg.html


To actually perform the migration, you can use some AWS tools such as SCT +
DMS:
https://docs.aws.amazon.com/prescriptive-guidance/latest/patterns/migrate-an-oracle-database-to-aurora-postgresql-using-aws-dms-and-aws-sct.html

Postgresql is a relational database just like Oracle, so database designs
(OLTP vs OLAP) are the same.
However, implementations of partitioning, indexing, isolation, etc... Those
have the same concept but some implementation differences.

Isolation, for instance, in Oracle you have the UNDO tablespace. In
Postgresql you have a different method that uses MVCC (Multi Version
Concurrency Control), which keeps deleted records (dead tuples), until a
vacuum process (or autovacuum) runs.
Performance, you have different memory parameters to adjust, hints. For
execution plan management, you need to install the Postgresql extension
apg_mgt_plan. I would recommend the following extension:

   - pgstattuple - row level statistics
   - pg_stat_statements - planning and execution of statistics
   - apg_mgmt_plan - for management of query plans
   - pg_cron - to schedule jobs

Index fragmentation occurs in Postgresql as well, so be sure to monitor it
because you may need to run a REINDEX CONCURRENTLY (in oracle INDEX REBUILD
ONLINE) when high fragmentation is observed.
Indexes in Postgresql have the INCLUDE option (which is similar to SQL
Server), which are columns to append to the index so you dont need to scan
the table.

Since you are going to Aurora Postgresql, it has the Performance Insights
tool which provides statistics and queries run against your Aurora Cluster.
You can enable it for free to have 7 days of statistics. It comes handy if
you are used to AWR in Oracle to investigate issues.




On Mon, Jan 15, 2024 at 1:43 PM Justin Clift  wrote:

> On 2024-01-15 14:16, veem v wrote:
> > Hello Experts,
> > If some teams are well versed with the Oracle database architecture and
> > its
> > optimizers working and designing applications on top of this. Now
> > moving
> > same team to work on AWS aurora postgresql databases design/development
> > projects. Is any key design/architectural changes should the app
> > development team or the database design team, should really aware
> > about, so
> > as to take right decision on any new development project in AWS aurora
> > postgresql database?
> > Or
> > Is there any list of differences(as compared to Oracle database) in key
> > concepts like for example basic design concepts, Normalization,
> > Partitioning, clustering, backup and recovery, Indexing strategy,
> > isolation
> > level, performance which one should definitely be aware of?
>
> Is this the kind of thing you're looking for?
>
>
>
> https://www.enterprisedb.com/blog/the-complete-oracle-to-postgresql-migration-guide-tutorial-move-convert-database-oracle-alternative
>
> Regards and best wishes,
>
> Justin Clift
>
>
>

-- 
Best Regards,
_
Henrique S. G. Lima
Mobile: +1 (204) 951-6191

Re: Help with "Create Extension unaccent"

2024-01-15 Thread Lan Xu 
Hi Adrian and Ian, 

Thank you for responding! 

OS: CentOS 7.9.2009
Postgres: 14.5

It was an upgrade from an older version. 

Thanks again! Thank you for your guidance!

Lan

> On Jan 14, 2024, at 8:50 AM, Adrian Klaver  wrote:
> 
> On 1/13/24 21:52, Lan Xu wrote:
>> With CREATE EXTENSION unaccent, I’m getting the following:
>> ERROR:  extension "unaccent" has no installation script nor update path for 
>> version “1.0"
>> But I can find it under /usr/share/pgsql/extension/unaccent001.0.sql
>> Thank you for your help!
> 
> What OS and version?
> 
> What Postgres version?
> 
> How did you install Postgres?
> 
>> Lan
> 
> -- 
> Adrian Klaver
> adrian.kla...@aklaver.com
>

Re: Help needed for the resolution of memory leak

2024-01-15 Thread Merlin Moncure 
On Mon, Jan 15, 2024 at 11:32 AM Sasmit Utkarsh 
wrote:

> Hi Team,
>
> I am trying to test a code which basically tries to read some data from
> postgresql db in a loop through a function SQL_get_tpf_rw() whose
> definition and other details are shared in the attached file along with the
> memory leak report resulted during testing. Could you let me know if i
> missed calling  anywhere PQclear()
> in SQL_get_tpf_rw() which resulted in the below .
>
> Last few lines from the report
>
>
yep:  for example,

  if (PQresultStatus(*res*) != PGRES_TUPLES_OK)
{
LOG_ERROR("SELECT failed: %s", PQerrorMessage(conn));
LOG_DEBUG("ROLLBACK TRANSACTION AND CHAIN");
*res* = PQexec(conn,"ROLLBACK TRANSACTION AND CHAIN");
LOG_ERROR("INVALID_FILE_ADDRESS %08X",fa);
rc = ERR_INVALID_FILE_ADDRESS;


See highlighted bits.  You're reusing the res object before clearing
it.  there may be other cases, but this jumped off the page.


merlin

Re: Moving to Postgresql database

2024-01-15 Thread Justin Clift 

On 2024-01-15 14:16, veem v wrote:

Hello Experts,
If some teams are well versed with the Oracle database architecture and 
its
optimizers working and designing applications on top of this. Now 
moving

same team to work on AWS aurora postgresql databases design/development
projects. Is any key design/architectural changes should the app
development team or the database design team, should really aware 
about, so

as to take right decision on any new development project in AWS aurora
postgresql database?
Or
Is there any list of differences(as compared to Oracle database) in key
concepts like for example basic design concepts, Normalization,
Partitioning, clustering, backup and recovery, Indexing strategy, 
isolation

level, performance which one should definitely be aware of?


Is this the kind of thing you're looking for?

  
https://www.enterprisedb.com/blog/the-complete-oracle-to-postgresql-migration-guide-tutorial-move-convert-database-oracle-alternative


Regards and best wishes,

Justin Clift

Re: multiple missing providers from pgdg-common

2024-01-15 Thread Joseph G 
I can confirm everything works now, Thank you!

Sent via mobile, please excuse typos and brevity.

On Mon, Jan 15, 2024, 02:20 Devrim Gündüz  wrote:

> Hi,
>
> On Sat, 2024-01-13 at 13:23 -0800, Joseph G wrote:
> > If we look, gdal35 or 36 is asking for libarmadillo.so.10 which
> > doesn't look like its available for EL8 just an older EL7?  I can't
> > get past this error at the moment.
>
> Pushed GDAL 3.6.4-6 RPMS to the repos built against armadillo 12 for
> RHEL 9, 8 and Fedora.
>
> Thanks for the report.
>
> Regards,
>
> --
> Devrim Gündüz
> Open Source Solution Architect, PostgreSQL Major Contributor
> Twitter: @DevrimGunduz , @DevrimGunduzTR
>

Re: data migration using EXTENSION tds_fdw

2024-01-15 Thread Adrian Klaver 



On 1/15/24 11:03 AM, Eyüp Liste wrote:

Hello,

1)TURKISH_CI_AS at sql server database

2)Encoding : UTF8 Collate: en_US.UTF-8  at Postgresql


I don't use tds_fdw, so the best I can do is point you at information

Hopefully someone with practical experience will chime in with more 
specific information.


The information I could find is:

https://www.freetds.org/userguide/configs.html#Localization












Thank u for fast response

Best Regards

Eyup Liste
Senior Database Administrator
___

TurkNet Iletisim







M: +905452120762
E: eyup.li...@turk.net

-Original Message-
From: Adrian Klaver 
Sent: Monday, January 15, 2024 7:10 PM
To: Eyüp Liste ; pgsql-general@lists.postgresql.org
Subject: Re: data migration using EXTENSION tds_fdw


[UYARI] Bu ileti TurkNet dışından gönderildi. Lütfen gönderen adresleri kontrol 
edin ve ekleri açmadan önce dikkatli olun.
Spam/phishing olduğunu düşündüğünüz mailler için 
spambil...@turknet.net.tr adresine bilgi 
verebilirsiniz.


On 1/14/24 10:55, Eyüp Liste wrote:

Hello,

I have worked on migrate a table from sql server 2017 to postgresql 15 .
İ have completed all steps. But when i try to migrate some columns , i
got error;

NOTICE: tds_fdw: Query executed correctly NOTICE: tds_fdw: Getting
results ERROR: DB-Library error: DB #: 2403, DB Msg: Some character(s)
could not be converted into client's character set. Unconverted bytes
were changed to question marks ('?'), OS #: 0, OS Msg: Success, Level:
4 SQL state: HV00L

This "Some character(s) could not be converted into client's character set." 
would seem to be the issue.

Therefore what is the character set used in the?:

1) The SQL Server database.

2) The Postgres database


Please help me about this issue.

Best regards

*turknet-logo* **



*Eyüp Liste*
Technology
System And Infrastructure


--
Adrian Klaver
adrian.kla...@aklaver.com

Re: Unable to find column

2024-01-15 Thread Adrian Klaver 

On 1/15/24 09:26, arun chirappurath wrote:

Hi Adrian,

\d shows the tables and this id which is a sequence.


What I asked for was the output of:

\d automobile

Add that output to your reply.



Regards,
Arun




--
Adrian Klaver
adrian.kla...@aklaver.com

Re: Unable to find column

2024-01-15 Thread arun chirappurath 
Hi Adrian,

\d shows the tables and this id which is a sequence.

Regards,
Arun

On Mon, 15 Jan 2024 at 22:03, Adrian Klaver 
wrote:

> On 1/15/24 08:16, arun chirappurath wrote:
> > Dear all,
> >
> > I have a table automobile which has a column id.
> >
> > Table consists of id,make,year of manufacturing
> >
> > I use dbeaver for querying..
> >
> > Select * from automobile provides me results
> >
> > However select id from automobile yields column doesn't exists.
> >
> > I tried double quotes on id As well but same error.
> >
> > But if I drag and drop id or use the id which is auto prompted from
> > dbeaver,it works 💪.
> >
> > select "id" from automobile using drag and drop of id in dbeaver works.
> >
> > But if I manually type "id" it won't.
> >
> > Any clue on this.
>
> Do you have psql(https://www.postgresql.org/docs/current/app-psql.html(
> available?
>
> If so in psql what does:
>
> \d automobile
>
> return?
>
>
> >
> > Visually both statements are alike
> >
> >
> > Table is in public schema.
> >
> > Thanks,
> > Arun
> >
> >
> >
> >
>
> --
> Adrian Klaver
> adrian.kla...@aklaver.com
>
>

Re: Unable to find column

2024-01-15 Thread Adrian Klaver 

On 1/15/24 08:16, arun chirappurath wrote:

Dear all,

I have a table automobile which has a column id.

Table consists of id,make,year of manufacturing

I use dbeaver for querying..

Select * from automobile provides me results

However select id from automobile yields column doesn't exists.

I tried double quotes on id As well but same error.

But if I drag and drop id or use the id which is auto prompted from 
dbeaver,it works 💪.


select "id" from automobile using drag and drop of id in dbeaver works.

But if I manually type "id" it won't.

Any clue on this.


Do you have psql(https://www.postgresql.org/docs/current/app-psql.html( 
available?


If so in psql what does:

\d automobile

return?




Visually both statements are alike


Table is in public schema.

Thanks,
Arun






--
Adrian Klaver
adrian.kla...@aklaver.com

Re: Unable to find column

2024-01-15 Thread Ian Harding 
On Mon, Jan 15, 2024 at 8:17 AM arun chirappurath 
wrote:

> Dear all,
>
> I have a table automobile which has a column id.
>
> Table consists of id,make,year of manufacturing
>
> I use dbeaver for querying..
>
> Select * from automobile provides me results
>
> However select id from automobile yields column doesn't exists.
>
> I tried double quotes on id As well but same error.
>
> But if I drag and drop id or use the id which is auto prompted from
> dbeaver,it works 💪.
>
> select "id" from automobile using drag and drop of id in dbeaver works.
>

Possibly there is a case sensitivity issue. If you use double quotes the
string is protected and searched for with explicit case. If not it is
folded to lower case.

I don’t know about dbeaver but I suspect case sensitivity.

>
> But if I manually type "id" it won't.
>
> Any clue on this.
>
> Visually both statements are alike
>
>
> Table is in public schema.
>
> Thanks,
> Arun
>
>
>
>
>

Unable to find column

2024-01-15 Thread arun chirappurath 
Dear all,

I have a table automobile which has a column id.

Table consists of id,make,year of manufacturing

I use dbeaver for querying..

Select * from automobile provides me results

However select id from automobile yields column doesn't exists.

I tried double quotes on id As well but same error.

But if I drag and drop id or use the id which is auto prompted from
dbeaver,it works 💪.

select "id" from automobile using drag and drop of id in dbeaver works.

But if I manually type "id" it won't.

Any clue on this.

Visually both statements are alike


Table is in public schema.

Thanks,
Arun

Re: Add support for data change delta tables

2024-01-15 Thread Adrian Klaver 

On 1/15/24 02:44, Thomas Kellerer wrote:

PavelTurk schrieb am 15.01.2024 um 11:00:

Currently PostgreSQL doesn't support data change delta tables. For example, it 
doesn't support this type of query:

SELECT * FROM NEW TABLE (
 INSERT INTO phone_book
 VALUES ( 'Peter Doe', '555-2323' )
) AS t

PostgreSQL has RETURNING that provides only a subset of this functionality.

So I suggest to add support for data change delta tables. Because this feature 
is more powerful and it is included
in the SQL Standard.


I don't know that syntax, but it seems to me, it's basically this:

with t as (
INSERT INTO phone_book
VALUES ( 'Peter Doe', '555-2323' )
returning *
)
select *
from t;




There is also transition relations:

https://www.postgresql.org/docs/current/sql-createtrigger.html

though that involves creating a trigger on a table.

--
Adrian Klaver
adrian.kla...@aklaver.com

Re: data migration using EXTENSION tds_fdw

2024-01-15 Thread Adrian Klaver 

On 1/14/24 10:55, Eyüp Liste wrote:

Hello,

I have worked on migrate a table from sql server 2017 to postgresql 15 . 
İ have completed all steps. But when i try to migrate some columns , i 
got error;


NOTICE: tds_fdw: Query executed correctly NOTICE: tds_fdw: Getting 
results ERROR: DB-Library error: DB #: 2403, DB Msg: Some character(s) 
could not be converted into client's character set. Unconverted bytes 
were changed to question marks ('?'), OS #: 0, OS Msg: Success, Level: 4 
SQL state: HV00L


This "Some character(s) could not be converted into client's character 
set." would seem to be the issue.


Therefore what is the character set used in the?:

1) The SQL Server database.

2) The Postgres database



Please help me about this issue.

Best regards

*turknet-logo* **



*Eyüp Liste*
Technology
System And Infrastructure



--
Adrian Klaver
adrian.kla...@aklaver.com

Postgres authorization ad groups

2024-01-15 Thread Czajkowski Łukasz 
Hello

I wondering about login to postgres with different method such ldap connected 
with ident. Same ldap don't make problem but I think about authorization by 
ldap and further automatic switch usera to another user. I think about 
authorization for only one group of active directory. Does it is possible?

I mean:
User is authorize by ldap and if is member examply groups, user can login to 
db. After authorization user is switching to another share user in postgres. 
Share user is use by all users who are members group.

Generally it is loging for users from selected group. Is it possible in 
postgres?

Regards
Łukasz Czajkowski




T-MOBILE POLSKA S.A. z siedzibą w Warszawie
Adres: ul. Marynarska 12, 02-674 Warszawa
Zarząd Spółki:
Andreas Maierhofer - Prezes Zarządu;
Juraj Andráš - Członek Zarządu, Dyrektor ds. Finansowych;
Dorota Kuprianowicz-Legutko - Członek Zarządu, Dyrektor ds. Polityki 
Personalnej;
Goran Marković - Członek Zarządu, Dyrektor ds. Rynku Prywatnego;
Alexander Jenbar - Członek Zarządu, Dyrektor ds. Technologii i Innowacji;
Agnieszka Rynkowska - Członek Zarządu, Dyrektor ds. Rynku Biznesowego.
Spółka zarejestrowana w Sądzie Rejonowym dla m.st. Warszawy w Warszawie,
XIII Wydział Gospodarczy Krajowego Rejestru Sądowego.
KRS 391193 | NIP 526-10-40-567 | Regon 011417295
Kapitał zakładowy 711.210.000 złotych, kapitał wpłacony w całości.

DUŻE ZMIANY ZACZYNAJĄ SIĘ OD MAŁYCH - CHROŃ PLANETĘ, NIE DRUKUJ TEGO E-MAILA, 
JEŻELI NIE MUSISZ.

Ta wiadomość i jej treść są zastrzeżone w szczegółowym zakresie dostępnym na 
http://www.t-mobile.pl/stopka
This e-mail and its contents are subject to a DISCLAIMER with important 
RESERVATIONS: see http://www.t-mobile.pl/stopka

data migration using EXTENSION tds_fdw

2024-01-15 Thread Eyüp Liste 

Hello,
I have worked on migrate a table from sql server 2017 to postgresql 15 . İ have 
completed all steps. But when i try to migrate some columns , i got error;

NOTICE: tds_fdw: Query executed correctly NOTICE: tds_fdw: Getting results 
ERROR: DB-Library error: DB #: 2403, DB Msg: Some character(s) could not be 
converted into client's character set. Unconverted bytes were changed to 
question marks ('?'), OS #: 0, OS Msg: Success, Level: 4 SQL state: HV00L

Please help me about this issue.

Best regards
[turknet-logo]

Eyüp Liste
Technology
System And Infrastructure

Re: Add support for data change delta tables

2024-01-15 Thread Thomas Kellerer 
PavelTurk schrieb am 15.01.2024 um 11:00:
> Currently PostgreSQL doesn't support data change delta tables. For example, 
> it doesn't support this type of query:
> 
> SELECT * FROM NEW TABLE (
> INSERT INTO phone_book
> VALUES ( 'Peter Doe', '555-2323' )
> ) AS t
> 
> PostgreSQL has RETURNING that provides only a subset of this functionality.
> 
> So I suggest to add support for data change delta tables. Because this 
> feature is more powerful and it is included
> in the SQL Standard.

I don't know that syntax, but it seems to me, it's basically this:

with t as (
   INSERT INTO phone_book
   VALUES ( 'Peter Doe', '555-2323' )
   returning *
)
select *
from t;

Re: Add support for data change delta tables

2024-01-15 Thread Pavel Stehule 
po 15. 1. 2024 v 11:27 odesílatel PavelTurk 
napsal:

>
> On 1/15/24 12:17 PM, Pavel Stehule wrote:
>
>
>
> po 15. 1. 2024 v 11:11 odesílatel PavelTurk 
> napsal:
>
>>
>> On 1/15/24 12:05 PM, Pavel Stehule wrote:
>>
>> Hi
>>
>> po 15. 1. 2024 v 11:00 odesílatel PavelTurk 
>> napsal:
>>
>>> Hello all,
>>>
>>>
>>> Currently PostgreSQL doesn't support data change delta tables. For example, 
>>> it doesn't support this type of query:
>>>
>>> SELECT * FROM NEW TABLE (
>>>  INSERT INTO phone_book
>>>  VALUES ( 'Peter Doe', '555-2323' )
>>> ) AS t
>>>
>>>
>>> PostgreSQL has RETURNING that provides only a subset of this functionality.
>>>
>>>
>>> So I suggest to add support for data change delta tables. Because this 
>>> feature is more powerful and it is included
>>> in the SQL Standard.
>>>
>>
>> This is the wrong mailing list - probably you should send your proposal
>> to pgsql-hackers.
>>
>>
>> I sent message to pgsql-hackers
>> https://www.postgresql.org/message-id/b85900eb-9e3c-e358-aa8f-5a27b30c17e7%40gmail.com
>> but got no answer. I decided that my message was ignored because I used
>> wrong mailing list.
>>
>> The community development is based on patches. If you propose some
>> feature,  usually you should implement it. Probably nobody will implement
>> it instand you.
>>
>>
>> I am Java developer - I wish, but I can't
>>
>
> I am sorry, but you cannot expect, so somebody will accept your proposal
> extra seriously. Proposing some feature is a simple thing, but implementing
> some not trivial feature requires hundreds of hours of development.
>
>
> To tell the truth I find it rather strange. I know that there is a big
> difference between proposing some feature and implementing it. But all
> projects I came across with work this way -
> you as a user come and propose a feature. The developers of the project
> consider your issue and either accept it to implement or decline it.
>

PostgreSQL is not a project where somebody says, you will do this, and you
will do this, in this and this priority. There are a lot of nice features
from standard - SQL standard is big, but a) you have to have funds to pay
the developers, b) you have to have developers with free time who want to
do free work. Sure, you can write a proposal, but without a) money or b)
your hard work is not a big possibility so your proposal will be
implemented in the next few years. With the patch the situation is
different. Then developers can see, so it is possible to implement, and how
much code (and work) needs it.



> You can check the work on features for Postgres
> https://commitfest.postgresql.org/ and I don't think so there is a lot of
> free capacity for implementing some new features partially redundant to
> already supported features.
>
> Regards
>
> Pavel
>
>
>
>> Best regards, Pavel
>>
>>
>

Re: Add support for data change delta tables

2024-01-15 Thread PavelTurk 


On 1/15/24 12:17 PM, Pavel Stehule wrote:



po 15. 1. 2024 v 11:11 odesílatel PavelTurk mailto:pavelturk2...@gmail.com>> napsal:


On 1/15/24 12:05 PM, Pavel Stehule wrote:

Hi

po 15. 1. 2024 v 11:00 odesílatel PavelTurk mailto:pavelturk2...@gmail.com>> napsal:

Hello all,

Currently PostgreSQL doesn't support data change delta tables. For 
example, it doesn't support this type of query:

SELECT * FROM NEW TABLE (
 INSERT INTO phone_book
 VALUES ( 'Peter Doe', '555-2323' )
) AS t

PostgreSQL has RETURNING that provides only a subset of this 
functionality.

So I suggest to add support for data change delta tables. Because this 
feature is more powerful and it is included
in the SQL Standard.


This is the wrong mailing list - probably you should send your proposal to 
pgsql-hackers.


I sent message to pgsql-hackers 
https://www.postgresql.org/message-id/b85900eb-9e3c-e358-aa8f-5a27b30c17e7%40gmail.com
 

but got no answer. I decided that my message was ignored because I used 
wrong mailing list.


The community development is based on patches. If you propose some feature, 
 usually you should implement it. Probably nobody will implement it instand you.


I am Java developer - I wish, but I can't


I am sorry, but you cannot expect, so somebody will accept your proposal extra 
seriously. Proposing some feature is a simple thing, but implementing some not 
trivial feature requires hundreds of hours of development.



To tell the truth I find it rather strange. I know that there is a big 
difference between proposing some feature and implementing it. But all projects 
I came across with work this way -
you as a user come and propose a feature. The developers of the project 
consider your issue and either accept it to implement or decline it.


You can check the work on features for Postgres https://commitfest.postgresql.org/ 
 and I don't think so there is a lot of 
free capacity for implementing some new features partially redundant to already 
supported features.

Regards

Pavel



Best regards, Pavel

Re: multiple missing providers from pgdg-common

2024-01-15 Thread Devrim Gündüz 
Hi,

On Sat, 2024-01-13 at 13:23 -0800, Joseph G wrote:
> If we look, gdal35 or 36 is asking for libarmadillo.so.10 which
> doesn't look like its available for EL8 just an older EL7?  I can't
> get past this error at the moment.

Pushed GDAL 3.6.4-6 RPMS to the repos built against armadillo 12 for
RHEL 9, 8 and Fedora.

Thanks for the report.

Regards,

-- 
Devrim Gündüz
Open Source Solution Architect, PostgreSQL Major Contributor
Twitter: @DevrimGunduz , @DevrimGunduzTR

Re: Add support for data change delta tables

2024-01-15 Thread Pavel Stehule 
po 15. 1. 2024 v 11:11 odesílatel PavelTurk 
napsal:

>
> On 1/15/24 12:05 PM, Pavel Stehule wrote:
>
> Hi
>
> po 15. 1. 2024 v 11:00 odesílatel PavelTurk 
> napsal:
>
>> Hello all,
>>
>>
>> Currently PostgreSQL doesn't support data change delta tables. For example, 
>> it doesn't support this type of query:
>>
>> SELECT * FROM NEW TABLE (
>>  INSERT INTO phone_book
>>  VALUES ( 'Peter Doe', '555-2323' )
>> ) AS t
>>
>>
>> PostgreSQL has RETURNING that provides only a subset of this functionality.
>>
>>
>> So I suggest to add support for data change delta tables. Because this 
>> feature is more powerful and it is included
>> in the SQL Standard.
>>
>
> This is the wrong mailing list - probably you should send your proposal to
> pgsql-hackers.
>
>
> I sent message to pgsql-hackers
> https://www.postgresql.org/message-id/b85900eb-9e3c-e358-aa8f-5a27b30c17e7%40gmail.com
> but got no answer. I decided that my message was ignored because I used
> wrong mailing list.
>
> The community development is based on patches. If you propose some
> feature,  usually you should implement it. Probably nobody will implement
> it instand you.
>
>
> I am Java developer - I wish, but I can't
>

I am sorry, but you cannot expect, so somebody will accept your proposal
extra seriously. Proposing some feature is a simple thing, but implementing
some not trivial feature requires hundreds of hours of development.

You can check the work on features for Postgres
https://commitfest.postgresql.org/ and I don't think so there is a lot of
free capacity for implementing some new features partially redundant to
already supported features.

Regards

Pavel



> Best regards, Pavel
>
>

Re: Add support for data change delta tables

2024-01-15 Thread PavelTurk 


On 1/15/24 12:05 PM, Pavel Stehule wrote:

Hi

po 15. 1. 2024 v 11:00 odesílatel PavelTurk mailto:pavelturk2...@gmail.com>> napsal:

Hello all,

Currently PostgreSQL doesn't support data change delta tables. For example, 
it doesn't support this type of query:

SELECT * FROM NEW TABLE (
 INSERT INTO phone_book
 VALUES ( 'Peter Doe', '555-2323' )
) AS t

PostgreSQL has RETURNING that provides only a subset of this functionality.

So I suggest to add support for data change delta tables. Because this 
feature is more powerful and it is included
in the SQL Standard.


This is the wrong mailing list - probably you should send your proposal to 
pgsql-hackers.


I sent message to pgsql-hackers 
https://www.postgresql.org/message-id/b85900eb-9e3c-e358-aa8f-5a27b30c17e7%40gmail.com
but got no answer. I decided that my message was ignored because I used wrong 
mailing list.


The community development is based on patches. If you propose some feature,  
usually you should implement it. Probably nobody will implement it instand you.


I am Java developer - I wish, but I can't

Best regards, Pavel

Re: Add support for data change delta tables

2024-01-15 Thread Pavel Stehule 
Hi

po 15. 1. 2024 v 11:00 odesílatel PavelTurk 
napsal:

> Hello all,
>
>
> Currently PostgreSQL doesn't support data change delta tables. For example, 
> it doesn't support this type of query:
>
> SELECT * FROM NEW TABLE (
>  INSERT INTO phone_book
>  VALUES ( 'Peter Doe', '555-2323' )
> ) AS t
>
> PostgreSQL has RETURNING that provides only a subset of this functionality.
>
>
> So I suggest to add support for data change delta tables. Because this 
> feature is more powerful and it is included
> in the SQL Standard.
>

This is the wrong mailing list - probably you should send your proposal to
pgsql-hackers.

https://wiki.postgresql.org/wiki/Developer_FAQ

The community development is based on patches. If you propose some
feature,  usually you should implement it. Probably nobody will implement
it instand you.

Regards

Pavel



>
> Best regards, Pavel
>
>
>

Add support for data change delta tables

2024-01-15 Thread PavelTurk 

Hello all,

Currently PostgreSQL doesn't support data change delta tables. For example, it 
doesn't support this type of query:

SELECT * FROM NEW TABLE (
INSERT INTO phone_book
VALUES ( 'Peter Doe', '555-2323' )
) AS t

PostgreSQL has RETURNING that provides only a subset of this functionality.

So I suggest to add support for data change delta tables. Because this feature 
is more powerful and it is included
in the SQL Standard.

Best regards, Pavel