~launchpad-pqm/launchpad/devel

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
-- Copyright 2011 Canonical Ltd.  This software is licensed under the
-- GNU Affero General Public License version 3 (see the file LICENSE).

SET client_min_messages=ERROR;


-- Create a journal for BugSummary updates.
-- This is a separate DB patch as the table needs to be created and
-- added to replication before triggers are created, and we want to
-- do this live. We discussed not replicating this table, but this
-- would break our ability to failover to a new master.

CREATE TABLE BugSummaryJournal (
    id serial PRIMARY KEY,
    count INTEGER NOT NULL default 0,
    product INTEGER REFERENCES Product ON DELETE CASCADE,
    productseries INTEGER REFERENCES ProductSeries ON DELETE CASCADE,
    distribution INTEGER REFERENCES Distribution ON DELETE CASCADE,
    distroseries INTEGER REFERENCES DistroSeries ON DELETE CASCADE,
    sourcepackagename INTEGER REFERENCES SourcePackageName ON DELETE CASCADE,
    viewed_by INTEGER,
    tag TEXT,
    status INTEGER NOT NULL,
    milestone INTEGER REFERENCES Milestone ON DELETE CASCADE);

-- Fat index for fast lookups
CREATE INDEX bugsummaryjournal__full__idx ON BugSummaryJournal (
    status, product, productseries, distribution, distroseries,
    sourcepackagename, viewed_by, milestone, tag);

-- Indexes for fast deletions.
CREATE INDEX bugsummaryjournal__viewed_by__idx
    ON BugSummaryJournal(viewed_by) WHERE viewed_by IS NOT NULL;
CREATE INDEX bugsummaryjournal__milestone__idx
    ON BugSummaryJournal(milestone) WHERE milestone IS NOT NULL;


-- Combined view so we don't have to manually collate rows from both tables.
-- Note that we flip the sign of the id column of BugSummaryJournal to avoid
-- clashes. This is enough to keep Storm happy as it never needs to update
-- this table, and there are no other suitable primary keys.
-- We don't SUM() rows here to ensure PostgreSQL has the most hope of
-- generating good query plans when we query this view.
CREATE OR REPLACE VIEW CombinedBugSummary AS (
    SELECT
        id, count, product, productseries, distribution, distroseries,
        sourcepackagename, viewed_by, tag, status, milestone
    FROM BugSummary
    UNION ALL
    SELECT
        -id as id, count, product, productseries, distribution, distroseries,
        sourcepackagename, viewed_by, tag, status, milestone
    FROM BugSummaryJournal);

INSERT INTO LaunchpadDatabaseRevision VALUES (2208, 63, 3);