On Mon, Jun 11, 2018 at 10:12 AM, a <372660...@qq.com> wrote:
> Hey, the following is the table :
> 1 1 1 "f" 1 "2018-06-11 11:38:33.163731+08" "00:00:00.033002" "Couldn't
> get a connection to the database!"
> 2 2 1 "f" 1 "2018-06-11 11:45:03.406061+08" "00:00:00.033002" "Couldn't
> get a
Hey, the following is the table :
1 1 1 "f" 1 "2018-06-11 11:38:33.163731+08"
"00:00:00.033002" "Couldn't get a connection to the database!"
2 2 1 "f" 1 "2018-06-11 11:45:03.406061+08"
"00:00:00.033002" "Couldn't get a
On Mon, Jun 11, 2018 at 9:56 AM, a <372660...@qq.com> wrote:
> Hey thanks so much.
>
> I found the error msg as "Couldn't get a connection to the database!"
>
> I've searched internet with the issue, some may say replace pgpass.conf as
> follow:
>
> "*localhost:5432:[dbname]:postgres:[password]*"
Hey thanks so much.
I found the error msg as "Couldn't get a connection to the database!"
I've searched internet with the issue, some may say replace pgpass.conf as
follow:
"localhost:5432:[dbname]:postgres:[password]"
but after I changed, the job returns a "i" as last result, which is a
Please use "pgadmin-supp...@postgresql.org" for any pgAdmin/pgAgent related
questions, bugs.
On Mon, Jun 11, 2018 at 9:33 AM, a <372660...@qq.com> wrote:
> Hi all
>
> I set up a pgagent job, but it says the job was failed.
>
> But where I can have a look on error report message??
>
> I'm using
Hi
I'm setting up agent jobs for postgresql. I'm on win server 2008, and
postgresql 10.
I set up the jobs using pgadmin 4.3.
however, the job is not executing, may I ask why??
On 06/10/2018 02:45 PM, Alexander Shutyaev wrote:
Comments inline.
The error log is like this. Here's its tail:
Is this the regular Postgres log or the pg_upgrade log which should be
something like pg_upgrade_server.log?
pg_restore: [archiver (db)] could not execute query: ERROR:
The error log is like this. Here's its tail:
pg_restore: executing BLOB 1740737401
pg_restore: WARNING: database with OID 0 must be vacuumed within 103
transactions
HINT: To avoid a database shutdown, execute a database-wide VACUUM in that
database.
You might also need to commit or roll
On 06/10/2018 02:09 PM, Alexander Shutyaev wrote:
Some more notes on databses.
Although the pg_upgrade failed, I've decided to check the databases in
the new cluster (10.4). There is no database with oid 0 either. Also to
be noted that some system databases changed the oids while others
Some more notes on databses.
Although the pg_upgrade failed, I've decided to check the databases in the
new cluster (10.4). There is no database with oid 0 either. Also to be
noted that some system databases changed the oids while others retained
them.
And of my databases - sslentry. It had a
No database with oid 0 in 9.6 cluster:
postgres=# select oid, datname from pg_database;
oid | datname
+---
1 | template1
12438 | template0
16400 | bof
12439 | postgres
1016305714 | sslentry
(5 rows)
>> 1) OS and version you are using?
I can provide you with more info. Please tell me what you need. I really
hope someone here can help me somehow solve or workaround this, because I
really need to migrate to v10 for its features.
Thanks in advance,
Alexander
2018-06-09 22:52 GMT+03:00 Tom Lane :
> Adrian Klaver writes:
> > On
I can provide you with more info. Please tell me what you need. I really hope
someone here can help me somehow solve or workaround this, because I really
need to migrate to v10 for its features.
Thanks in advance,
Alexander
--
Sent from:
On 06/05/2018 07:58 AM, Nicolas Seinlet wrote:
Hi,
I've tried some tests, by generating various datas in
the res_currency_rate table.
If I generate res_currency_rate rows for unsused currencies, this
doesn't influence the execution time.
if I generate more res_currency_rate for used
14 matches
Mail list logo
