snapshots are created over and over again Postgres #20
Comments
|
I now notice this comment in the source |
|
Weird, can you look into tests and provide a failing test case?
…On Sun, Mar 25, 2018, 22:52 Bas Kamer ***@***.***> wrote:
from docker log
postgres_1 | 2018-03-25 14:42:45.795 UTC [26] ERROR: duplicate key value violates unique constraint "projections_name_key"
postgres_1 | 2018-03-25 14:42:45.795 UTC [26] DETAIL: Key (name)=(snapshot:customer_customer) already exists.
postgres_1 | 2018-03-25 14:42:45.795 UTC [26] STATEMENT: INSERT INTO "projections" (name, position, state, status, locked_until)
postgres_1 | VALUES ($1, '{}', '{}', $2, NULL);
postgres_1 | 2018-03-25 14:42:45.899 UTC [26] ERROR: duplicate key value violates unique constraint "projections_name_key"
postgres_1 | 2018-03-25 14:42:45.899 UTC [26] DETAIL: Key (name)=(snapshot:dossier_dossier) already exists.
postgres_1 | 2018-03-25 14:42:45.899 UTC [26] STATEMENT: INSERT INTO "projections" (name, position, state, status, locked_until)
postgres_1 | VALUES ($1, '{}', '{}', $2, NULL);
postgres_1 | 2018-03-25 14:42:45.992 UTC [26] ERROR: duplicate key value violates unique constraint "projections_name_key"
postgres_1 | 2018-03-25 14:42:45.992 UTC [26] DETAIL: Key (name)=(snapshot:dossier_order) already exists.
postgres_1 | 2018-03-25 14:42:45.992 UTC [26] STATEMENT: INSERT INTO "projections" (name, position, state, status, locked_until)
postgres_1 | VALUES ($1, '{}', '{}', $2, NULL);
postgres_1 | 2018-03-25 14:42:46.083 UTC [26] ERROR: duplicate key value violates unique constraint "projections_name_key"
postgres_1 | 2018-03-25 14:42:46.083 UTC [26] DETAIL: Key (name)=(snapshot:filesystem_file) already exists.
postgres_1 | 2018-03-25 14:42:46.083 UTC [26] STATEMENT: INSERT INTO "projections" (name, position, state, status, locked_until)
postgres_1 | VALUES ($1, '{}', '{}', $2, NULL);
postgres_1 | 2018-03-25 14:42:46.179 UTC [26] ERROR: duplicate key value violates unique constraint "projections_name_key"
postgres_1 | 2018-03-25 14:42:46.179 UTC [26] DETAIL: Key (name)=(snapshot:identity_user) already exists.
postgres_1 | 2018-03-25 14:42:46.179 UTC [26] STATEMENT: INSERT INTO "projections" (name, position, state, status, locked_until)
postgres_1 | VALUES ($1, '{}', '{}', $2, NULL);
postgres_1 | 2018-03-25 14:42:46.280 UTC [26] ERROR: duplicate key value violates unique constraint "projections_name_key"
postgres_1 | 2018-03-25 14:42:46.280 UTC [26] DETAIL: Key (name)=(snapshot:sop_workflow) already exists.
postgres_1 | 2018-03-25 14:42:46.280 UTC [26] STATEMENT: INSERT INTO "projections" (name, position, state, status, locked_until)
postgres_1 | VALUES ($1, '{}', '{}', $2, NULL);
At first I thought is was because of the : in the name, however changing
that to - didn't solve it.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#20>, or mute the
thread
<https://github.com/notifications/unsubscribe-auth/AAYEvDvIycDkyDsFNXvVDPw3fCHLuoGOks5th68ygaJpZM4S6Kw1>
.
|
|
Where is that comment? Can't remember everything, sorry :-) |
|
Ah okay, that's in pdo-event-store, not snapshot store, so other repo. What
you can do to eliminate errors is create pdo connection with attribute to
disable exceptions. Can't remember the name though. We check statement
error info always, so no need to enable pdo exception.
…On Sun, Mar 25, 2018, 23:03 Bas Kamer ***@***.***> wrote:
https://github.com/prooph/pdo-event-store/blob/f9d8fe7d3df7d4b91bca531bb367ac5319bf11b3/src/Projection/PdoEventStoreProjector.php#L719
https://github.com/prooph/pdo-event-store/blob/f9d8fe7d3df7d4b91bca531bb367ac5319bf11b3/src/Projection/PdoEventStoreReadModelProjector.php#L668
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#20 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAYEvGJjKRCIyvEtgfG3ZBSHSzNJaCnsks5th7HOgaJpZM4S6Kw1>
.
|
|
Setting these options will not suppress this output into the postgres logs. Time to install log rotate on my docker logs. |
|
ah postgres logs, okay, yes you can't do anything about it. sorry. |
|
i can find these, if that's what your looking for : https://dba.stackexchange.com/questions/38817/on-duplicate-key-do-nothing or https://dba.stackexchange.com/questions/30499/optimal-way-to-ignore-duplicate-inserts |
|
|
|
cool, wanna provide another PR ? |
|
yes, but need to prioritise, so later |
|
no problem, thanks |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
from docker log
At first I thought is was because of the : in the name, however changing that to - didn't solve it.
The text was updated successfully, but these errors were encountered: