compact catalogue failed?

Post Reply
bimo
Posts: 148
Joined: 29 Aug 07 22:34
Location: Germany

compact catalogue failed?

Post by bimo » 27 Apr 18 17:26

1. compacted catalogue before installing build 1436: OK
2. installed 1436; did this and that: everything fine
3. did a compact again: well... have a look by yourself
compact psu1436.jpg
compact psu1436.jpg (11.16 KiB) Viewed 1686 times
Disturbing, isn't it? Anyone any explanation?
Michael

Hert
Posts: 21501
Joined: 13 Sep 03 7:24

Re: compact catalogue failed?

Post by Hert » 28 Apr 18 10:41

Can always be that Postgres or the network has a hickup while connecting. I assume the database is still there? During a compact PSU tells the database to rebuild its indexes and vacuum unused table space.
https://www.postgresql.org/docs/10/stat ... acuum.html
This is a User-to-User forum which means that users post questions here for other users.
Feature requests, change suggestions, or bugs can be logged in the ticketing system

bimo
Posts: 148
Joined: 29 Aug 07 22:34
Location: Germany

Re: compact catalogue failed?

Post by bimo » 14 May 18 14:27

Well,well, well: looks like this is a newly build-in function since 4.1.0.1436.

I installed POSTGRESQL 10.3 on a dedicated PC (win10 build 1803) and afterwards created a fresh db for PSu with
  • PSu 4.0.1.1023 - compact worked fine
  • PSu 4.0.1.1201 - compact worked fine
  • PSu 4.1.0.1410 - compact worked fine
  • PSu 4.1.0.1436 - no compact /see error-msg above
  • PSu 4.1.0.1465 - no compact /see error-msg above
  • PSu 4.1.0.1486 - no compact /see error-msg above
Looks like a problem in PSu, doesn't it?
Michael

Hert
Posts: 21501
Joined: 13 Sep 03 7:24

Re: compact catalogue failed?

Post by Hert » 14 May 18 15:26

It works fine here, and if it works fine here then there's little I can do.
https://cp.idimager.com/support/Videos/ ... atalog.mp4
(I'm using PostgreSQL 10.1)

I know that several other regular visitors here also use the PostgreSQL version. Maybe they can reply if it works for them?

1. Is the name of your Photo Supreme database indeed "Produktionskatalog"?
2. Have you tried to Vacuum the database with pgAdmin?

Not relevant but thought I'd mention anyway; compacting the database is not as important for the Server Edition (PostgreSQL as well as SQLServer) as it is for the Single User (SQLite) edition. That is because these database systems are less prone to fragmentation than SQLite.
This is a User-to-User forum which means that users post questions here for other users.
Feature requests, change suggestions, or bugs can be logged in the ticketing system

larmstrong
Posts: 27
Joined: 30 Jul 15 21:28

Re: compact catalogue failed?

Post by larmstrong » 26 Nov 18 18:54

Has there been any update to this error?

Username
Posts: 197
Joined: 18 Feb 18 22:21

Re: compact catalogue failed?

Post by Username » 26 Nov 18 20:40

I'm doing a compacting of the catalogue db running 4.30.1755 Postgres.
And even though the PSu application shows a spinning beach ball and 0.0% progress even after 10 minutes, the server was working hard.
Although a single thread of postgres processing at 100%. After 15 minutes the 100% load from the postgres it dropped to zero.

The PSu is still at 0.0% progress.

Will let It keep working and see what happens further on.
- I'm the user

Hert
Posts: 21501
Joined: 13 Sep 03 7:24

Re: compact catalogue failed?

Post by Hert » 28 Nov 18 12:24

Username wrote:
26 Nov 18 20:40
The PSu is still at 0.0% progress.
Compacting a catalog doesn't show progress. It lists that compact is active and waits for it to finish.
This is a User-to-User forum which means that users post questions here for other users.
Feature requests, change suggestions, or bugs can be logged in the ticketing system

Username
Posts: 197
Joined: 18 Feb 18 22:21

Re: compact catalogue failed?

Post by Username » 28 Nov 18 17:17

Thanks Hert.

In the end PSu crashed for me but the compacting went through ok.
- I'm the user

Post Reply