diff options
| author | martinko | 2014-10-29 08:40:10 +0000 |
|---|---|---|
| committer | martinko | 2014-10-29 08:40:10 +0000 |
| commit | ce44959442968b3a641dfe462739597290d28b8e (patch) | |
| tree | 241c19ba12530e36a60fea72dda45dbeb9532321 | |
| parent | 4d05530822584b22bd8fa29af39483cf4f3705f6 (diff) | |
sql/pgq_ext/structure/tables.sql: fixed some typos
| -rw-r--r-- | sql/pgq_ext/structure/tables.sql | 10 |
1 files changed, 5 insertions, 5 deletions
diff --git a/sql/pgq_ext/structure/tables.sql b/sql/pgq_ext/structure/tables.sql index 78a1b234..f916c86f 100644 --- a/sql/pgq_ext/structure/tables.sql +++ b/sql/pgq_ext/structure/tables.sql @@ -1,14 +1,14 @@ -- ---------------------------------------------------------------------- -- Section: Tables -- --- The pgq_ext schema exists to help in making sure that allenents get --- processed and they get processed only once +-- The pgq_ext schema exists to help in making sure that all events get +-- processed and they get processed only once. -- --- Simple quidelines for avoiding duplicate events: +-- Simple guidelines for avoiding duplicate events: -- -- It is pretty burdensome to check if event is already processed, --- especially on bulk data moving. Here's a way how checking --- individual event checks can be avoided by tracking processing of batches. +-- especially on bulk data moving. Here's a way how individual +-- event checks can be avoided by tracking processing of batches. -- -- First, consumer must guarantee that it processes all events in one tx. -- |