| Age | Commit message (Collapse) | Author |
|---|
|
|
|
|
|
|
|
The goal is to leave no "garbage" that accumulates over time.
|
|
let's get trendy ... it's no good to be stuck on same minor version for so long ;-)
and it actually did not make sense ... quite a few important features appeared
|
|
|
|
That case was broken in old 9.1 releases, fixed since 9.1.7.
The sequence will be owned by extension and without tagging
it will not be dumped in data dump.
|
|
|
|
Not needed and now logutriga() behavior matches
skytools.db_urlencode() and urllib.quote_plus().
|
|
|
|
mostly works now.
only problem is that londiste_writer needs to be
superuser because of session_replication_role.
That can be fixed with secdef function, but that
means code needs to be installed separately.
|
|
Now unpatched naturaldocs should work fine.
|
|
|
|
Info-notices are warnings now.
Needed to ignore different notices in 9.3
|
|
|
|
|
|
when subconsumer was given on input
|
|
|
|
Quoting was not done previosly as the table names
come not from user input but from internal tables.
But understanding whether it's safe in particular setup requires
extra thinking which is not good. So to remove the need for thinking,
lets quote everything properly.
|
|
Hopefully this makes it more clear how to upgrade 2.1.
|
|
|
|
Seems there aretoo many places where version needs to be mentioned..
|
|
Needed for pgq & pgq_coop that have changed.
Also move more common code to common-pgxs.mk
|
|
Everything is 3.1.0.0 now.
|
|
This means it's value will be lost during dump+restore.
|
|
Keep installing old module files under contrib/ still.
|
|
|
|
|
|
|
|
Otherwise we cannot use insert_event on branch nodes.
We could allow it in 'local' role too, but another kind-of-valid
behaviour is to skip insert completely in 'local' role.
So until a valid use-case appers, don't ignore the flag
in 'local' role.
|
|
|
|
This is attempt for fine-grained access rights for all
Skytools SQL schemas. As it still needs review,
the rights are not activated by default, instead
following sql files are generated:
newgrants_<schema>.sql - applies new rights, drop old public access
oldgrants_<schema>.sql - restores old rights - public execute
privilege to all functions
Only thing that is active by default is creation of new
groups in upgrade functions.
New access roles:
pgq_reader
Can consume queues (source-side)
pgq_writer
Can write into queues (source-side / dest-side)
Can use pgq_node/pgq_ext schema as regular
consumer (dest-side)
pgq_admin
Admin operations on queues, required for CascadedWorker on dest-side.
Member of pgq_reader and pgq_writer.
londiste_reader
Member of pgq_reader, needs additional read access to tables.
(source-side)
londiste_writer
Member of pgq_admin, needs additional write access to tables.
(dest-side)
|
|
|
|
|
|
|
|
By Hannu Krosing, applied with some fixing
|
|
|
|
|
|
It's obsolete since 8.3. Drop it.
|
|
|
|
Previously the need for step2 was decided by need for step1.
But if pgqd stops/crashed after step1 but before step2,
the step2 will not be run anymore.
Fix this by rechecking if no step1 was needed.
|
|
|
|
Old behaviour could catch (maybe) some bugs, but made
life hard for consumers that know what they are doing.
Basically, non-NULL tick pos is taken as "consumer knows better".
|
|
|
|
- use 'structure/upgrade.sql' to generate X.upgrade.sql
- add pgq_ext to upgraded schemas
- move non-standard upgrade scripts to extra/
- setup_skytools: build sql files in 'build' target, not always
- pgq_ext.version: bump ver to 3.0.0.1
|
|
|
|
|
|
- be silent if consumer does not exist
- if subconsumers exist, unregister those too
|
|
this allows to upgrade module without uprading schema.
|
|
|
