Re: Issue: Creating Symlink for data directory of postgresql in CentOS7

[Luca Ferrari]

On Sat, Jul 13, 2019 at 5:12 AM Chatterjee, Shibayan
 wrote:
> For sure there's all the necessary files in '/data/postgresql/data'. The 
> startup process cannot read it, because of sym link.
> Executing init-db return the below message:
>

I suspect this could be a systemd problem. What if you try to manually
start the postgres instance?

pg_ctl -D /data/postgresql/data start

What happens then?


>  # sudo postgresql-setup initdb
> Data directory is not empty!

This is of course to prevent you to destroy your system.
I would remove the link, create it to an empty directory and then
initdb such directory as if it is your new database. I imagine that
would start, in such case your data directory is wrong. Can you show
us the content of /data/postgresql/data?

Luca

Re: Testing an extension against multiple versions of Postgresql

[Luca Ferrari]

On Sat, Jul 13, 2019 at 8:03 AM Ian Barwick  wrote:
> > So the questions are:
> > Can I have make install & make installcheck run against multiple versions 
> > at the same time or how do I tell the installcheck to run against the 11 
> > server.
>
> Try setting relevant environment variables [*] for the target version before 
> running "make installcheck".
>
> [*] https://www.postgresql.org/docs/current//libpq-envars.html
>

Aside that, a possible easy way to test something against different
PostgreSQL instance is to use something like pgenv
, that is for instance used to test
sqitch.

Luca

Re: Issue: Creating Symlink for data directory of postgresql in CentOS7

[Laurenz Albe]

On Fri, 2019-07-12 at 18:08 +, Chatterjee, Shibayan wrote:
> > Jul 12 10:00:51 postgresql-check-db-dir: "/data/postgresql/data" is missing 
> > or empty.
> > Jul 12 10:00:51 postgresql-check-db-dir: Use "postgresql-setup initdb" to 
> > initialize the database cluster.
> > Jul 12 10:00:51 postgresql-check-db-dir: See 
> > /usr/share/doc/postgresql-9.2.24/README.rpm-dist for more information.
>
> For sure there's all the necessary files in '/data/postgresql/data'.
> The startup process cannot read it, because of sym link.

Well, where is the source for this fabled "postgresql-check-db-dir"?

Yours,
Laurenz Albe
-- 
Cybertec | https://www.cybertec-postgresql.com

Re: Testing an extension against multiple versions of Postgresql

[Rhys A.D. Stewart]

Thanks!!

Rhys
Peace & Love|Live Long & Prosper


On Sat, Jul 13, 2019 at 3:15 AM Luca Ferrari  wrote:

> On Sat, Jul 13, 2019 at 8:03 AM Ian Barwick 
> wrote:
> > > So the questions are:
> > > Can I have make install & make installcheck run against multiple
> versions at the same time or how do I tell the installcheck to run against
> the 11 server.
> >
> > Try setting relevant environment variables [*] for the target version
> before running "make installcheck".
> >
> > [*] https://www.postgresql.org/docs/current//libpq-envars.html
> >
>
> Aside that, a possible easy way to test something against different
> PostgreSQL instance is to use something like pgenv
> , that is for instance used to test
> sqitch.
>
> Luca
>

Re: Postgresql and VBA - Connection Timeout

[Wayne Mell]

Hello Hiroshi,

Thank you for your reply.

Your suggestion to try setting cnn.CommandTimeout = 0   before calling 
cnn.Execute() worked perfectly and was exactly the solution I needed.  Since 
the cnn connection was what owned the Execute, it was the object that needed 
the Command Timeout.  That is a much nicer solution than editing the DLL.

I am very grateful for your help.

Thank you,

Wayne


From: Inoue, Hiroshi 
Sent: Friday, July 12, 2019 7:53 PM
To: Wayne Mell
Cc: Adrian Klaver; pgsql-general@lists.postgresql.org; 
pgsql-o...@lists.postgresql.org
Subject: Re: Postgresql and VBA - Connection Timeout

Hi Wayne,

On 2019/07/13 0:05, Wayne Mell wrote:
Thank you Adrian,

The link you sent had an answer that worked.

I had to edit the psqlodbc35w.dll file and change SET statement_timeout =  %d 
to SET statement_timeout =  0 .

Somewhere in the thread, Hiroshi Inoue mentioned that a SQL_QUERY_TIMEOUT 
statement was built into the driver starting with version 9.5 of the driver, 
but all of my attempts to find documentation on how to use this feature in VBA 
have failed.

It certainly would be a better way to handle this.  Can anyone point me at some 
documentation?  I've copied this to the ODBC list as well.

Thanks everyone who replied.

Wayne




From: Adrian Klaver 

Sent: Thursday, July 11, 2019 3:21 PM
To: Wayne Mell; 
pgsql-general@lists.postgresql.org
Subject: Re: Postgresql and VBA - Connection Timeout

On 7/11/19 1:04 PM, Wayne Mell wrote:
> Can someone help me with executing a postgres function from VBA?  No
> matter what function I call, it always times out after exactly 30
> seconds.  I've tried to use the statement_timeout a million different
> ways and always get an error that states "Cancelling statement due to
> statement timeout" in Access.
>
> Here is the code I've been using to test:
>
> Dim cnn As ADODB.Connection
> Dim cnnCmd As ADODB.Command
>
>   Set cnn = New ADODB.Connection
> cnn.ConnectionString = "Driver={PostgreSQL
> Unicode(x64)};Server=postgres.office.server;Port=5432;Database=DBS;UID=postgresuser;PWD=postgrespwd;"
> cnn.ConnectionTimeout = 0
> cnn.Open
>


> Set cnnCmd = New ADODB.Command
> cnnCmd.CommandTimeout = 0

ISTM the above 2 lines  are meaningless because the cnnCmd isn't use by the 
following
cnn.Execute command.

>
> Set cnnCmd = cnn.Execute("select pg_sleep(50);")

Could you Please try

calling cnnCmd.Execute() after setting cnnCmd.commandText

or

setting cnn.CommandTimeout = 0 before calling cnn.Execute()

?

regards,
Hiroshi Inoue

>
> There are other functions that I've tried to execute, and they all work
> as long as they take less than 30 seconds to run.  I just started
> running pg_sleep to test.
>
> If I log into pgAdmin with the same user name and password, and on the
> same machine, then the functions will execute no matter how long they
> take.  It's only through VBA and the psqlODBC driver that I have the 30
> second timeout limit.
>
> Has anyone found a way to make this work?  Thanks.


https://www.postgresql-archive.org/BUG-odbc-statement-timeout-gets-set-to-3-td5992591.html

>
>


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

[https://ipmcdn.avast.com/images/icons/icon-envelope-tick-green-avg-v1.png]
 ウイルス フリー。 
www.avg.com

Re: Issue: Creating Symlink for data directory of postgresql in CentOS7

[Adrian Klaver]

On 7/13/19 4:30 AM, Laurenz Albe wrote:

On Fri, 2019-07-12 at 18:08 +, Chatterjee, Shibayan wrote:

Jul 12 10:00:51 postgresql-check-db-dir: "/data/postgresql/data" is missing or 
empty.
Jul 12 10:00:51 postgresql-check-db-dir: Use "postgresql-setup initdb" to 
initialize the database cluster.
Jul 12 10:00:51 postgresql-check-db-dir: See 
/usr/share/doc/postgresql-9.2.24/README.rpm-dist for more information.


For sure there's all the necessary files in '/data/postgresql/data'.
The startup process cannot read it, because of sym link.


Well, where is the source for this fabled "postgresql-check-db-dir"?


https://git.postgresql.org/gitweb/?p=pgrpms.git;a=blob;f=rpm/redhat/9.2/postgresql/EL-7/postgresql92-check-db-dir;h=550b31770cabacf32cbb1b8f272e8ce305fc9908;hb=HEAD



Yours,
Laurenz Albe




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