Driver Postgresql HP-Unix
Hi, Everyone
I have an Oracle database Oracle 19c and I need to access a PostgreSQL database
15.4 that resides on a different server. I see that one alternative is to use
ODBC from Oracle. However, the server where the database resides is an HP-UX
server and I understand that I need a PostgreSQL driver manager compatible with
this operating system. Can you help me by indicating if there is one available,
where to obtain it, and if it requires a license?
Thanks so much
ADVERTENCIA. La informaci?n de este correo, as? como sus documentos adjuntos,
puede ser objeto de solicitudes de acceso a la informaci?n; as? como, de
solicitudes en el ejercicio de los derechos de Acceso, Rectificaci?n,
Cancelaci?n y Oposici?n (ARCO). Este mensaje y cualquier archivo adjunto al
mismo pueden contener informaci?n que podr?a considerarse confidencial y/o
reservada. Si ha recibido el mensaje por error, por favor notifique al
remitente contestando el correo, y destruyendo el mensaje original y sus
anexos, como una medida de seguridad de car?cter administrativo, conforme a lo
establecido en el art?culo 3, fracci?n XXI de la Ley General de Protecci?n de
Datos Personales en Posesi?n de Sujetos Obligados. Su reproducci?n, parcial o
total, revisi?n, uso, revelaci?n, y/o distribuci?n indebida o no autorizada
puede constituir un delito y/o contravenir diversas disposiciones legales. Con
independencia de lo anterior, los fideicomisos que integran FIRA ("Fondo de
Garant?a y Fomento para la Agricultura, Ganader?a y Avicultura" (FONDO); "Fondo
Especial para Financiamientos Agropecuarios" (FEFA); "Fondo Especial de
Asistencia T?cnica y Garant?a para Cr?ditos Agropecuarios" (FEGA); "Fondo de
Garant?a y Fomento para las Actividades Pesqueras" (FOPESCA)); y Fideicomiso de
Pensiones del Fondo de Garant?a y Fomento para la Agricultura, Ganader?a y
Avicultura se reservan el derecho de ejercer las acciones que correspondan,
entre otros, por da?os y perjuicios, con motivo del empleo indebido y/o no
autorizado de la propia informaci?n. FIRA ha tomado precauciones para prevenir
que el presente correo est? infectado por virus, por lo que no acepta, entre
otros, responsabilidad alguna por da?os o p?rdidas causadas por el uso del
mismo o de los archivos adjuntos. Asimismo, le informamos que FIRA es
responsable de la protecci?n de los datos personales que trate. Dicho
tratamiento se llevar? a cabo conforme a lo previsto en la Ley General de
Protecci?n de Datos Personales en Posesi?n de Sujetos Obligados, con sujeci?n a
las atribuciones y facultades que la normatividad aplicable le confiere, y para
finalidades acordes a estas. Le invitamos a consultar nuestros avisos de
privacidad en nuestra p?gina de internet (www.fira.gob.mx), en la secci?n "Ley
de Transparencia", subsecci?n "Avisos de Privacidad".
Build fails on RHEL 8.8 about libxml2 version
Hello, Trying to build PostgreSQL 15 and 16 on RHEL 8.8: [comp@havok postgresql-15.1]$ cat /etc/redhat-release Red Hat Enterprise Linux release 8.8 (Ootpa) [comp@havok postgresql-15.1]$ uname -a Linux havok.strasbourg.4js.com 4.18.0-477.27.1.el8_8.x86_64 #1 SMP Thu Aug 31 10:29:22 EDT 2023 x86_64 x86_64 x86_64 GNU/Linux I got an error about libxml2 invalid version. checking for inflate in -lz... yes checking for xmlSaveToBuffer in -lxml2... no configure: error: library 'xml2' (version >= 2.6.23) is required for XML support But I see a 2.9.7: [comp@havok postgresql-15.1]$ find /lib64/ -name "libxml2*" /lib64/libxml2.so.2 /lib64/libxml2.so.2.9.7 /lib64/girepository-1.0/libxml2-2.0.typelib /lib64/python3.6/site-packages/__pycache__/libxml2.cpython-36.opt-1.pyc /lib64/python3.6/site-packages/__pycache__/libxml2.cpython-36.pyc /lib64/python3.6/site-packages/libxml2.py /lib64/python3.6/site-packages/libxml2mod.so What am I missing here? Seb
Re: How can I accurately infer the output of a SELECT statement FROM a table with floating-point data type?
Hi, May be you think about this ? SELECT REAL_COLUMN, *to_char(REAL_COLUMN,'9.9') 6_significant_numbers_format *FROM TEST; Regards Tomek czw., 19 paź 2023 o 05:47 毛毛 napisał(a): > Hi, > > Do we have a rule by follow which one can accurately info the output of a > SELECT statment FROM a table with floating-point data type? > > I am working with PostgreSQL 16 and pgAdmin 7.6. > > Here is my SQL script: > > ``` > CREATE TABLE TEST (REAL_COLUMN real); > > INSERT INTO TEST > VALUES (12345.123456789); > > SELECT * FROM TEST; > ``` > > I consulted the following doc and found that the range of real type is 6 > decimal digits precision. > > https://www.postgresql.org/docs/current/datatype-numeric.html#DATATYPE-NUMERIC > > So I thought the output of the SELECT statement should be like: 12345.1 > with 6 digits in total. > But it turns out to be 12345.123 with 8 digits in total. > May I know why would this happen? > Do we have a rule I can use to infer the correct output of a > floating-point number without running the script? > > Thank you for your time and have a great day! > >
Re: Build fails on RHEL 8.8 about libxml2 version
Answering to myself: Of course I must install the "*-devel" packages Seb From: Sebastien Flaesch Sent: Thursday, October 19, 2023 10:36 AM To: pgsql-general@lists.postgresql.org Subject: Build fails on RHEL 8.8 about libxml2 version EXTERNAL: Do not click links or open attachments if you do not recognize the sender. Hello, Trying to build PostgreSQL 15 and 16 on RHEL 8.8: [comp@havok postgresql-15.1]$ cat /etc/redhat-release Red Hat Enterprise Linux release 8.8 (Ootpa) [comp@havok postgresql-15.1]$ uname -a Linux havok.strasbourg.4js.com 4.18.0-477.27.1.el8_8.x86_64 #1 SMP Thu Aug 31 10:29:22 EDT 2023 x86_64 x86_64 x86_64 GNU/Linux I got an error about libxml2 invalid version. checking for inflate in -lz... yes checking for xmlSaveToBuffer in -lxml2... no configure: error: library 'xml2' (version >= 2.6.23) is required for XML support But I see a 2.9.7: [comp@havok postgresql-15.1]$ find /lib64/ -name "libxml2*" /lib64/libxml2.so.2 /lib64/libxml2.so.2.9.7 /lib64/girepository-1.0/libxml2-2.0.typelib /lib64/python3.6/site-packages/__pycache__/libxml2.cpython-36.opt-1.pyc /lib64/python3.6/site-packages/__pycache__/libxml2.cpython-36.pyc /lib64/python3.6/site-packages/libxml2.py /lib64/python3.6/site-packages/libxml2mod.so What am I missing here? Seb
Re: Driver Postgresql HP-Unix
On 10/18/23 13:45, Abelardo Erazo Lopez wrote: Hi, Everyone I have an Oracle database Oracle 19c and I need to access a PostgreSQL database 15.4 that resides on a different server. I see that one alternative is to use ODBC from Oracle. However, the server where the database resides is an HP-UX server and I understand that I need a PostgreSQL driver manager compatible with this operating system. Can you help me by indicating if there is one available, where to obtain it, and if it requires a license? Postgresql 15.4 is running on an HP-UX server? -- Born in Arizona, moved to Babylonia.
My question about the transaction
Hi community, I am learning the transaction of the postgresql, and I try to test using these: ## terminal 1: postgres=# select * from t; number 1 (1 row) postgres=# update t set number = 2; UPDATE 1 postgres=# select * from t; number 2 (1 row) postgres=# select * from t; number 2 (1 row) postgres=# ## terminal 2: postgres=# create table t (number integer); CREATE TABLE postgres=# insert into t values (1); INSERT 0 1 postgres=# begin; BEGIN postgres=*# insert into t values (2); INSERT 0 1 postgres=*# select * from t; number 2 2 (2 rows) postgres=*# rollback; ROLLBACK My question is, in my view, the transaction model should make sure that when one on-process transaction don't commit itself, the data on this transaction shouldn't can be modified by other transaction(I the single-statement also be treated as a simple transaction), but why the update works?(I think terminal 1 will block until the terminal 2's transaction commit or rollback). Can someone share you opinion to me? Thanks in advance! Yours, Wen Yi
Re: My question about the transaction
On Thursday, October 19, 2023, Wen Yi wrote: > Hi community, > I am learning the transaction of the postgresql, and I try to test using > these: > You failed to show how the two sessions interleave. Also, your first session doesn’t use multi-statement transactions. postgres=# insert into t values (1); > INSERT 0 1 > postgres=# begin; > BEGIN > Session one can see this row and modify it just fine… David J.
Re: My question about the transaction
On 10/19/23 04:36, Wen Yi wrote: Hi community, I am learning the transaction of the postgresql, and I try to test using these: ## terminal 1: postgres=# select * from t; number 1 (1 row) postgres=# update t set number = 2; UPDATE 1 postgres=# select * from t; number 2 (1 row) postgres=# select * from t; number 2 (1 row) postgres=# ## terminal 2: postgres=# create table t (number integer); CREATE TABLE postgres=# insert into t values (1); INSERT 0 1 postgres=# begin; BEGIN postgres=*# insert into t values (2); INSERT 0 1 postgres=*# select * from t; number 2 2 (2 rows) postgres=*# rollback; ROLLBACK My question is, in my view, the transaction model should make sure that when one on-process transaction don't commit itself, the data on this transaction shouldn't can be modified by other transaction(I the single-statement also be treated as a simple transaction), but why the update works?(I think terminal 1 will block until the terminal 2's transaction commit or rollback). Can someone share you opinion to me? Assuming you did in order, where terminal 1 = t1 and terminal 2 = t2: t2 create table t (number integer); t2 insert into t values (1); t1 select * from t; t1 update t set number = 2; t1 select * from t; t2 begin; t2 insert into t values (2); t2 select * from t; t1 select * from t; t2 rollback; Then it is as David said, the commands in t1 see the inserted value of 1 in table t and updates it as they are running in autocommit as where the commands in t2 before the begin;. Autocommit commits on each successful completion of a command. You then start am explicit transaction is t2 that sees the updated row and then adds a new row, both of which are seen in the t2 transaction but not in the t1 session. My suggestion would be to read through this: https://www.postgresql.org/docs/current/transaction-iso.html several times. There is a lot going on there. Thanks in advance! Yours, Wen Yi -- Adrian Klaver adrian.kla...@aklaver.com
Re: My question about the transaction
By default, psql is configured with autocommit on. Use another administrator, like phpadmin, and configure the connection with autocommit off. Atte JRBM El jue, 19 oct 2023 a las 11:49, Wen Yi () escribió: > Hi community, > I am learning the transaction of the postgresql, and I try to test using > these: > > ## > > terminal 1: > > postgres=# select * from t; > number > > 1 > (1 row) > > postgres=# update t set number = 2; > UPDATE 1 > postgres=# select * from t; > number > > 2 > (1 row) > > postgres=# select * from t; > number > > 2 > (1 row) > > postgres=# > > ## > > terminal 2: > > postgres=# create table t (number integer); > CREATE TABLE > postgres=# insert into t values (1); > INSERT 0 1 > postgres=# begin; > BEGIN > postgres=*# insert into t values (2); > INSERT 0 1 > postgres=*# select * from t; > number > > 2 > 2 > (2 rows) > > postgres=*# rollback; > ROLLBACK > > My question is, in my view, the transaction model should make sure that > when one on-process transaction don't commit itself, the data on this > transaction shouldn't can be modified by other transaction(I the > single-statement also be treated as a simple transaction), but why the > update works?(I think terminal 1 will block until the terminal 2's > transaction commit or rollback). > Can someone share you opinion to me? > Thanks in advance! > > Yours, > Wen Yi > > >
Re: My question about the transaction
On Thursday, October 19, 2023, Juan Rodrigo Alejandro Burgos Mella < rodrigoburgosme...@gmail.com> wrote: > By default, psql is configured with autocommit on. > Use another administrator, like phpadmin, and configure the > connection with autocommit off. > No. Please leave autocommit on and incorporate explicit begin/commit commands into the script if you want to demonstrate concurrency behavior. David J.
