Hi,
we have a use case similar to auditing packages like pgMemento or Audit
Trigger 91plus – we are looking to keep an ordered history of certain write
transactions. I'm trying to understand the trade-offs between different
ways of getting that order, i.e., assigning numbers to transactions
2016-06-11 13:47 GMT+03:00 Greg Navis :
> I made some progress but I'm stuck. I'm focused on GiST for now. Please
> ignore sloppy naming for now.
>
> I made the following changes to pg_trgm--1.2.sql:
>
> CREATE TYPE pg_trgm_match AS (match TEXT, threshold REAL);
>
> CREATE
On 06/11/2016 01:39 AM, Thomas Kellerer wrote:
Dave Page schrieb am 10.06.2016 um 16:48:
I'm pleased to announce that the release of pgAdmin 4 v1.0 Beta 1 for
testing. You can find more details on the website:
Announcement: https://www.pgadmin.org/
Documentation:
I made some progress but I'm stuck. I'm focused on GiST for now. Please
ignore sloppy naming for now.
I made the following changes to pg_trgm--1.2.sql:
CREATE TYPE pg_trgm_match AS (match TEXT, threshold REAL);
CREATE OR REPLACE FUNCTION trgm_check_match(string TEXT, match
pg_trgm_match)
OK, I file a bug report.
-Ursprüngliche Nachricht-
Von: Julien Rouhaud [mailto:julien.rouh...@dalibo.com]
Gesendet: Samstag, 11. Juni 2016 11:28
An: Daniel Migowski ; pgsql-general@postgresql.org
Betreff: Re: [GENERAL] Why are no NEGATORS defined in the standard
Hello
On 11/06/2016 10:00, Daniel Migowski wrote:
> Hello,
>
> while trying to bake my own fixedpoint datatype I noticed the definition
> for =(int8,int8) to be
>
>
>
> CREATE OPERATOR =(
>
> PROCEDURE = int8eq,
>
> LEFTARG = int8,
>
> RIGHTARG = int8,
>
> COMMUTATOR = =,
>
>
Dave Page schrieb am 10.06.2016 um 16:48:
I'm pleased to announce that the release of pgAdmin 4 v1.0 Beta 1 for
testing. You can find more details on the website:
Announcement: https://www.pgadmin.org/
Documentation: https://www.pgadmin.org/docs4/dev/index.html
Downloads:
Hello,
while trying to bake my own fixedpoint datatype I noticed the definition for
=(int8,int8) to be
CREATE OPERATOR =(
PROCEDURE = int8eq,
LEFTARG = int8,
RIGHTARG = int8,
COMMUTATOR = =,
RESTRICT = eqsel,
JOIN = eqjoinsel,
HASHES,
MERGES);
in PostgreSQL 9.5, but I wonder,
On Sat, 11 Jun 2016 09:59:59 +0530
Sridhar N Bamandlapally wrote:
> Ok, let me put this way,
>
> I need every transaction coming from application sync with both
> production and archive db,
> but the transactions I do to clean old data(before 7 days) on
> production db in