Re: [HACKERS] How to determine that a TransactionId is really aborted?

> aborted-and-no-longer-considered-visible so I can clean up my external list. > so, what you want is txid_status() [1]... while this is new in v10 you can use the code as guide or just migrate to v10 ;) [1] https://www.postgresql.org/docs/10/static/functions-info.html#functions-txid-snapshot

Re: [HACKERS] Columnar storage support

On 9 October 2017 at 15:03, legrand legrand wrote: > Is there a chance that pluggable storage permits creation of a columnar rdbms > as monetDB in PostgreSQL ? pluggable storage is one of the pieces for it, yes... but is not as simple as that, IIUC -- Jaime Casanova

Re: [HACKERS] generated columns

On 10 September 2017 at 00:08, Jaime Casanova wrote: > > During my own tests, though, i found some problems: > a few more tests: create table t1 ( id serial, height_cm int, height_in int generated always as (height_cm * 10) ) ; """ postgres=# alter table t1 alte

Re: [HACKERS] generated columns

(11); server closed the connection unexpectedly This probably means the server terminated abnormally before or while processing the request. The connection to the server was lost. Attempting reset: Failed. !> \q -- Jaime Casanova www.2ndQuadrant.com PostgreSQL Development,

Re: [HACKERS] [PATCH] New command to monitor progression of long running queries

gt;> > Thank you for the patch. > sorry if i'm bikeshedding to soon but... why a command instead of a function? something like pg_progress_backend() will be in sync with pg_cancel_backend()/pg_terminate_backend() and the result of such a function could be usable by a tool to examine a s

[HACKERS] SASL minor docs typo

Hi, reading SASL docs found this typo: in protocol.sgml:1356 """ To begin a SASL authentication exchange, the server an AuthenticationSASL message. """ I guess it should say "the server sends an AuthenticationSASL message" -- Jaime Casanova

[HACKERS] minor typo in client-auth.sgml

cram md5 and password. """ -- Jaime Casanova www.2ndQuadrant.com PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers

Re: [HACKERS] Patch: Write Amplification Reduction Method (WARM)

uot;!(((bool) (((const void*)(&tup->t_ctid) != ((void *)0)) && (((&tup->t_ctid)->ip_posid & uint16) 1) << 13) - 1)) != 0", File: "../../../../src/include/access/htup_details.h", Line: 659) """ -- Jaime Casanova

Re: [HACKERS] [PATCH v1] Add and report the new "in_hot_standby" GUC pseudo-variable.

u going to know the current value of the GUC that makes it different to just poll for pg_is_in_recovery()? -- Jaime Casanova www.2ndQuadrant.com PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services -- Sent via pgsql-hackers mailing lis

Re: [HACKERS] Logical replication launcher's bgworker enabled by default, and max_logical_replication_workers

f code > diffs, it would be disabled by default. > +1, we should that to 0 before release -- Jaime Casanova www.2ndQuadrant.com PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services -- Sent via pgsql-hackers mailing list (pgsql-hackers@po

Re: [HACKERS] Logical Replication WIP

On 20 January 2017 at 11:39, Petr Jelinek wrote: > On 20/01/17 17:33, Jaime Casanova wrote: >>> >> >> surely wal_level < logical shouldn't start a logical replication >> launcher, and after an initdb wal_level is only replica >> > > Launcher is ne

Re: [HACKERS] Logical Replication WIP

efault. You'd need to set > max_logical_replication_workers to 0 to disable that. > surely wal_level < logical shouldn't start a logical replication launcher, and after an initdb wal_level is only replica -- Jaime Casanova www.2ndQuadrant.com PostgreSQL Develo

Re: [HACKERS] Patch: Write Amplification Reduction Method (WARM)

rtup due to startup process failure """ still cannot reproduce this one consistently but happens often enough will continue playing with it... -- Jaime Casanova www.2ndQuadrant.com PostgreSQL Development, 24x7 Support, Remote DBA, Training & Serv

Re: [HACKERS] patch proposal

at it's unable to restore that WAL > segment. > Ah! Is this documented somewhere? if we expect people to use correct exit codes we should document them, no? -- Jaime Casanova www.2ndQuadrant.com PostgreSQL Development, 24x7 Support, Remote DBA, Training & Service

Re: [HACKERS] Declarative partitioning - another take

On 7 November 2016 at 12:15, Jaime Casanova wrote: > On 28 October 2016 at 02:53, Amit Langote > wrote: >> >> Please find attached the latest version of the patches > > Hi, > > I started to review the functionality of this patch, so i applied all > 9 patches

Re: [HACKERS] Declarative partitioning - another take

t have any ideas there... except, there was a reason not to use expressions (like a CHECK constraint?) -- Jaime Casanova www.2ndQuadrant.com PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services failing_test_1.sql Description: application/sql fail

Re: [HACKERS] Is the last 9.1 release planned?

ppens is that all minor releases are released the same day. Taken your example, that same day were released: 9.0.23, 9.1.19, 9.2.14, 9.3.10 and 9.4.5 -- Jaime Casanova www.2ndQuadrant.com PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services -- Sent via

Re: [HACKERS] autonomous transactions

oo() line 7 at SQL statement STATEMENT: select foo(); ERROR: null value in column "i" violates not-null constraint DETAIL: Failing row contains (null). CONTEXT: PL/pgSQL function foo() line 7 at SQL statement this happens even everytime i use the PRAGMA even if no START TRANSA

Re: [HACKERS] autonomous transactions

ilty why do you want to put it in jail? -- Jaime Casanova www.2ndQuadrant.com PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers

Re: [HACKERS] to_date_valid()

is instead? Sounds like a bug to me. We don't usually want to be bug compatible so it doesn't matter if we break something. -- Jaime Casanovahttp://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Training & Services

[HACKERS] Rename synchronous_standby_names?

Hi, Are we going to change synchronous_standby_names? Certainly the GUC is not *only* a list of names anymore. synchronous_standby_config? synchronous_standbys (adjust to correct english if necesary)? -- Jaime Casanova www.2ndQuadrant.com PostgreSQL Development, 24x7

Re: [HACKERS] 10.0

Etc cetera. >>>> >>>> >>> Yes. Please! >> >> Hear, hear! >> >> Sadly, we're too late for 9.6, but we can start with 10.0 and finish >> this silliness once and for good. > > +1! > +1 -- Jaime Casanova

Re: [HACKERS] Disabling an index temporarily

n't something like: > > ALTER INDEX foo SET DISABLED; > > See more in line with our grammar? > > I assume the index is only disabled as far as the planner is concerned and > all updates/inserts/deletes will still actually update the index > appropriately?

Re: [HACKERS] REASSIGN OWNED doesn't know how to deal with USER MAPPINGs

On 10 December 2015 at 13:04, Jaime Casanova wrote: > Hi, > > We just notice $SUBJECT. Attached patch fixes it by ignoring USER > MAPPINGs in shdepReassignOwned() just like it happens with default > ACLs. > BTW, shouldn't we at least give a warning on those cases instead o

[HACKERS] REASSIGN OWNED doesn't know how to deal with USER MAPPINGs

Hi, We just notice $SUBJECT. Attached patch fixes it by ignoring USER MAPPINGs in shdepReassignOwned() just like it happens with default ACLs. DROP OWNED manages it well. -- Jaime Casanova www.2ndQuadrant.com Professional PostgreSQL: Soporte 24x7 y capacitación diff --git

Re: [HACKERS] GIN pending list clean up exposure to SQL

On 21 November 2015 at 03:54, Jim Nasby wrote: > On 11/19/15 10:47 AM, Jaime Casanova wrote: >> >> - only superusers? > > > I would think the owner of the table (index?) should also be able to run > this. agreed, that makes sense -- Jaime Casanova

Re: [HACKERS] GIN pending list clean up exposure to SQL

On 19 November 2015 at 14:57, Jaime Casanova wrote: > On 19 November 2015 at 14:47, Jaime Casanova > wrote: >> On 19 November 2015 at 14:18, Alvaro Herrera >> wrote: >>> Alvaro Herrera wrote: >>>> Jeff Janes wrote: >>>> > I've written

Re: [HACKERS] GIN pending list clean up exposure to SQL

On 19 November 2015 at 14:47, Jaime Casanova wrote: > On 19 November 2015 at 14:18, Alvaro Herrera wrote: >> Alvaro Herrera wrote: >>> Jeff Janes wrote: >>> > I've written a function which allows users to clean up the pending list. >>> > It takes t

Re: [HACKERS] GIN pending list clean up exposure to SQL

> > After reading gitPendingCleanup it becomes clear that there's no need > for a stronger lock than what you've chosen. Jaime Casanova just > pointed this out to me. > But it should do some checks, no? - only superusers? - what i received as parameter is a GIN index? -- Ja

Re: [HACKERS] GIN pending list clean up exposure to SQL

On 12 August 2015 at 20:19, Jeff Janes wrote: > > But where does this belong? Core? Its own separate extension? > I will say core. Gin indexes are in core and i don't see why this function shouldn't. FWIW, brin indexes has a similar function brin_summarize_new_values()

Re: [HACKERS] bugs and bug tracking

hich OS was affected that is the one the user was using. still the bug could happen in all OSes (versions?), only some, only a specifi OS in a specific version is affected. so we need, to have an interface to fix metada... and people taking responsability for that -- Jaime Casanova

Re: [HACKERS] bugs and bug tracking

nt to register in a ML, they just want a specific question answered so i don't think any change in the form will avoid that. -- Jaime Casanova www.2ndQuadrant.com Professional PostgreSQL: Soporte 24x7 y capacitación -- Sent via pgsql-hackers mailing lis

Re: [HACKERS] synchronous_commit = apply

n suggest is not the first time he submitted that option so it should be other threads too: http://www.postgresql.org/message-id/aanlktinxoymwowbsjxmnpjhjh_yan9vfmnmhnjdme...@mail.gmail.com -- Jaime Casanova www.2ndQuadrant.com Professional PostgreSQL: Soporte 24x7 y capacitació

Re: [HACKERS] Proposal: Implement failover on libpq connect level.

ver have multimaster included then this could be a good idea -- Jaime Casanova www.2ndQuadrant.com Professional PostgreSQL: Soporte 24x7 y capacitación -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers

Re: [HACKERS] Improving GEQO

ithout the code to look at -- Jaime Casanova www.2ndQuadrant.com Professional PostgreSQL: Soporte 24x7 y capacitación -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers

Re: [HACKERS] Remove fsync ON/OFF as a visible option?

On Sat, Mar 21, 2015 at 2:33 PM, Joshua D. Drake wrote: > > On 03/20/2015 11:28 PM, Jaime Casanova wrote: >> >> > >> I fought to remove fsync before so i understand JD concerns. and yes, >> i have seen fsync=off in the field too... >> >> wha

Re: [HACKERS] Remove fsync ON/OFF as a visible option?

El mar 21, 2015 2:00 AM, "Mark Kirkwood" escribió: > > On 21/03/15 19:28, Jaime Casanova wrote: >> >> what about not removing it but not showing it in postgresql.conf? as a >> side note, i wonder why trace_sort is not in postgresql.conf... >> other option i

Re: [HACKERS] Remove fsync ON/OFF as a visible option?

why trace_sort is not in postgresql.conf... other option is to make it a compile setting, that why if you want to have it you need to compile and postgres' developers do that routinely anyway just my 2c -- Jaime Casanova www.2ndQuadrant.com Professional PostgreSQL: Soporte 24x7 y

Re: [HACKERS] pgaudit - an auditing extension for PostgreSQL

foo ..." queries (by > any user). what if i want to audit different things for different users? -- Jaime Casanova www.2ndQuadrant.com Professional PostgreSQL: Soporte 24x7 y capacitación Phone: +593 4 5107566 Cell: +593 987171157 -- Sent via pgsql-hackers mailing list (pgsql-

Re: [HACKERS] TABLESAMPLE patch

count(1) from tenk1 tablesample system (null); count --- 28 (1 row) regression=# select count(1) from tenk1 tablesample bernoulli (null); count --- 0 (1 row) """ -- Jaime Casanova www.2ndQuadrant.com Professional PostgreSQL: Soporte 24x7 y capacitación Pho

Re: [HACKERS] Commitfest problems

27;s kind of frustrating when some not-yet customers ask for certificated engineers, and there isn't any official (as in "from community") certificate so you need to prove you're a contributor so let's see this random commit messages... -- Jaime Casanova www.2ndQuad

Re: [HACKERS] Postgres TR for missing chunk

ady fixed and you should update. http://www.postgresql.org/message-id/12138.1336019...@sss.pgh.pa.us Btw, when giving a bug report you should start but saying your PostgreSQL's version and explain what you did based on Google's "wisdom" -- Jaime Casanova 2ndQuadrant Consultant Your PostgreSQL partner

Re: [HACKERS] TABLESAMPLE patch

the patch more close tomorrow when my brain wake up ;) -- Jaime Casanova www.2ndQuadrant.com Professional PostgreSQL: Soporte 24x7 y capacitación Phone: +593 4 5107566 Cell: +593 987171157 regression.diffs Description: Binary data -- Sent via pgsql-hackers mailing list (pg

Re: [HACKERS] Turning recovery.conf into GUCs

On Mon, Nov 24, 2014 at 12:24 PM, Jaime Casanova wrote: > On Fri, Nov 21, 2014 at 12:55 PM, Josh Berkus wrote: >> On 11/21/2014 09:35 AM, Alex Shulgin wrote: >>> Hello, >>> >>> Here's an attempt to revive this patch. >> >> Yayy! Thank you

Re: [HACKERS] Turning recovery.conf into GUCs

s were suggested "standby.enabled" transmit the wrong idea > Personally, if we have three methods of promotion: > > 1) pg_ctl promote > 2) edit postgresql.conf and reload > 3) ALTER SYSTEM SET and reload > > ... I don't honestly think we need a 4th method fo

Re: [HACKERS] Amazon Redshift

k at the examples you will see they only copy ours and changed the values a little. -- Jaime Casanova www.2ndQuadrant.com Professional PostgreSQL: Soporte 24x7 y capacitación Phone: +593 4 5107566 Cell: +593 987171157 -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.or

Re: [HACKERS] Let's drop two obsolete features which are bear-traps for novices

ing period. > Not knowing how difficult it could be maybe a fair compromise is to move MONEY datatype to a contrib. And documenting its limitations. -- Jaime Casanova 2ndQuadrant Consultant PostgreSQL Development, 24x7 Support, Training & Services

Re: [HACKERS] Shared Data Structure b/w clients

t or any link > to follow. > you can look at contrib/pg_stat_statements -- Jaime Casanova www.2ndQuadrant.com Professional PostgreSQL: Soporte 24x7 y capacitación Phone: +593 4 5107566 Cell: +593 987171157 -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)

Re: [HACKERS] Minmax indexes

his different from "ALTER TABLE foo SET (FILLFACTOR=80); " or from "ALTER TABLE foo ALTER bar SET STORAGE EXTERNAL; " ? we don't get a notice for these cases either -- Jaime Casanova www.2ndQuadrant.com Professional PostgreSQL: Soporte 24x7 y capacita

Re: [HACKERS] view reloptions

ched is a patch moving the reloptions of views into its own structure. i also created a view_reloptions() function in order to not use heap_reloptions() for views, but maybe that was too much? i haven't seen the check_option_offset thingy yet, but i hope to take a look at that tomorrow. -- J

Re: [HACKERS] Providing catalog view to pg_hba.conf file - Patch submission

so, i think you should use lowercase values just they are in pg_hba.conf (ie: local not Local, host not Host, etc) -- Jaime Casanova www.2ndQuadrant.com Professional PostgreSQL: Soporte 24x7 y capacitación Phone: +593 4 5107566 Cell: +593 987171157 -- Sent via pgsql-h

Re: [HACKERS] SQL access to database attributes

On Fri, May 23, 2014 at 11:06 PM, Vik Fearing wrote: > On 05/24/2014 12:03 AM, Jaime Casanova wrote: >> On Fri, May 23, 2014 at 10:53 PM, Vik Fearing wrote: >>> It was suggested to me that these options should either error out if >>> there are existing connections or

Re: [HACKERS] SQL access to database attributes

ase (how else do you modify it?), and adding a reject rule in > pg_hba.conf doesn't disconnect existing users so why should turning off > ALLOW CONNECTIONS do it? > Which lead us to the question: you need to connect to the database to modify it, don't you? then, how do you chang

Re: [HACKERS] [WIP] showing index maintenance on EXPLAIN

On Thu, May 8, 2014 at 10:44 PM, Amit Kapila wrote: > On Thu, May 8, 2014 at 12:01 PM, Jaime Casanova wrote: >> On Wed, May 7, 2014 at 10:52 PM, Amit Kapila wrote: >>> >>> Why to capture only for Index Insert/Update and not for Read; is it >>> because Read w

Re: [HACKERS] [WIP] showing index maintenance on EXPLAIN

On Thu, May 8, 2014 at 10:41 AM, Robert Haas wrote: > On Thu, May 8, 2014 at 2:31 AM, Jaime Casanova wrote: >> On Wed, May 7, 2014 at 10:52 PM, Amit Kapila wrote: >>> On Thu, May 8, 2014 at 5:30 AM, Jaime Casanova >>> wrote: >>>> Hi, >>>> &g

Re: [HACKERS] [WIP] showing index maintenance on EXPLAIN

On Wed, May 7, 2014 at 10:52 PM, Amit Kapila wrote: > On Thu, May 8, 2014 at 5:30 AM, Jaime Casanova wrote: >> Hi, >> >> This patch implements $subject only when ANALYZE and VERBOSE are on. >> I made it that way because for years nobody seemed interested in this >

Re: [HACKERS] [WIP] showing index maintenance on EXPLAIN

On Wed, May 7, 2014 at 7:03 PM, Josh Berkus wrote: > On 05/07/2014 05:00 PM, Jaime Casanova wrote: >> Hi, >> >> This patch implements $subject only when ANALYZE and VERBOSE are on. >> I made it that way because for years nobody seemed interested in this >> i

[HACKERS] [WIP] showing index maintenance on EXPLAIN

we have GiST and GIN this became an interested piece of data (there are other cases even when using btree). Current patch doesn't have docs yet i will add them soon. -- Jaime Casanova www.2ndQuadrant.com Professional PostgreSQL: Soporte 24x7 y capacitación Phone: +593 4 51

[HACKERS] server vs foreign server inconsistency

at all IMHO i think 3 is not acceptable because it's annoying opinions? -- Jaime Casanova www.2ndQuadrant.com Professional PostgreSQL: Soporte 24x7 y capacitación Phone: +593 4 5107566 Cell: +593 987171157 -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresq

Re: [HACKERS] Patch for CREATE RULE sgml -- Was in: [DOCS]

ossible is already listed in the section > "Parameters" => "event": AFAIU, the synopsis is used to build the help command (\h) in psql. Currently in that help the events doesn't appear. btw, CREATE TRIGGER already looks this way: http://www.postgresql.org/doc

Re: [HACKERS] db_user_namespace a "temporary measure"

On Tue, Mar 11, 2014 at 10:52 PM, Andrew Dunstan wrote: > > On 03/11/2014 11:50 PM, Jaime Casanova wrote: >> >> On Tue, Mar 11, 2014 at 10:06 PM, Tom Lane wrote: >>> >>> But not sure how to define a unique >>> index that allows (joe, db1) to coe

Re: [HACKERS] db_user_namespace a "temporary measure"

fy the db then is the global 'joe' that want to login -- Jaime Casanova www.2ndQuadrant.com Professional PostgreSQL: Soporte 24x7 y capacitación Phone: +593 4 5107566 Cell: +593 987171157 -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make c

Re: [HACKERS] 9.2.1 & index-only scans : abnormal heap fetches after VACUUM FULL

iteheap.c:433 #7 0x0055c373 in reform_and_rewrite_tuple (tuple=tuple@entry=0x1852a50, oldTupDesc=oldTupDesc@entry=0x7f9a3da4d350, newTupDesc=newTupDesc@entry=0x7f9a3da599a8, values=values@entry=0x1852f40, isnull=isnull@entry=0x184f920 "", newRelHasOids=1 '\001', rwstate=rwst

Re: [HACKERS] Trigger information for auto_explain.

_triggers_v1_20140114.patch > > Enable auto_explain to output trigger information. > > Documentation will be added later.. > Hi, I think documentation is the only thing that stops this patch to be commitable... can you add it? -- Jaime Casanova www.2ndQuadrant.c

Re: [HACKERS] Turning recovery.conf into GUCs

On Wed, Jan 15, 2014 at 2:00 AM, Jaime Casanova wrote: > On Mon, Nov 18, 2013 at 12:27 PM, Andres Freund > wrote: > >> * Maybe we should rename names like pause_at_recovery_target to >> recovery_pause_at_target? Since we already force everyone to bother >> ch

Re: [HACKERS] tracking commit timestamps

; LOG: database system was not properly shut down; automatic recovery in progress LOG: record with zero length at 0/3112AE58 LOG: redo is not required FATAL: cannot make new WAL entries during recovery LOG: startup process (PID 24876) exited with exit code 1 LOG: aborting startup due to startup p

Re: [HACKERS] Turning recovery.conf into GUCs

to >> facilitate maintenance across versions. > > I think lowercase is slightly more consistent with the majority of the > other GUCs, but if you change it you should change all the new GUC variables. > This one was my change, in the original patch is called "restore_c

Re: [HACKERS] Turning recovery.conf into GUCs

On Fri, Nov 15, 2013 at 9:28 AM, Peter Eisentraut wrote: > On 11/13/13, 12:17 AM, Jaime Casanova wrote: >> I have rebased Michael Paquier's patch and did a few changes: >> >> * changed standby.enabled filename to recovery.trigger >> * make archive_command a

Re: [HACKERS] Commitfest II CLosed

can give preference to patches of submitters that are also reviewing other people's patches. -- Jaime Casanova www.2ndQuadrant.com Professional PostgreSQL: Soporte 24x7 y capacitación Phone: +593 4 5107566 Cell: +593 987171157 -- Sent via pgsql-hackers mailing list (pgsql-hacke

Re: [HACKERS] Turning recovery.conf into GUCs

ude files ending in '.conf' from # directory 'conf.d' """ anything before this should be up to the packagers, no? or, do you mean something else? -- Jaime Casanova www.2ndQuadrant.com Professional PostgreSQL: Soporte 24x7 y capacitación

Re: [HACKERS] Turning recovery.conf into GUCs

ct tools that manage binary replication. > And, as I said before, we need to do the GUC merger in the same release > we introduce configuration directory (or after it). > you mean the ALTER SYSTEM syntax? anyway, why that restriction? -- Jaime Casanova www.2ndQuadrant.com

Re: [HACKERS] Turning recovery.conf into GUCs

don't want people to accidentally take a server > out of replication because they didn't check which version of PostgreSQL > they are on. > well, people will go out of replication also if they forgot the recovery trigger file even if they set the variables in postgresql.conf it hap

Re: [HACKERS] Turning recovery.conf into GUCs

a PITR recovery, I just put the recovery variables > into postgresql.conf, then? > create a recovery trigger file (called standby.enabled in current patch) in $PGDATA and start the server -- Jaime Casanova www.2ndQuadrant.com Professional PostgreSQL: Soporte 24x7 y capacitación Ph

Re: [HACKERS] Turning recovery.conf into GUCs

ER, REPLICATION_STANDBY, >> >> Not sure about these ones >> >> + {"recovery_target_timeline", PGC_POSTMASTER, WAL_RECOVERY_TARGET, >> + {"primary_conninfo", PGC_POSTMASTER, REPLICATION_STANDBY, > > It would be really nice to change these on th

[HACKERS] Turning recovery.conf into GUCs

very_target_timeline", PGC_POSTMASTER, WAL_RECOVERY_TARGET, + {"primary_conninfo", PGC_POSTMASTER, REPLICATION_STANDBY, This is the only one i agree, should be PGC_POSTMASTER only + {"standby_mode", PGC_POSTMASTER, REPLICATION_STANDBY, -- Jaime Casanova

Re: [HACKERS] [PoC] pgstattuple2: block sampling to reduce physical read

for good accuracy in every relation? why not a percentage, maybe an argument to the function? also the name pgstattuple2, doesn't convince me... maybe you can use pgstattuple() if you use a second argument (percentage of the sample) to overload the function -- Jaime Casanova www.2

Re: [HACKERS] Assertions in PL/PgSQL

El 21/09/2013 17:16, "Jaime Casanova" escribió: > > On Fri, Sep 20, 2013 at 5:17 AM, Marko Tiikkaja wrote: > > On 9/20/13 12:09 PM, Amit Khandekar wrote: > >> > >> On 16 September 2013 03:43, Marko Tiikkaja wrote: > >>> > >>> I t

Re: [HACKERS] VMs for Reviewers Available

#x27;re building from git anyway. > If you're reviewing patches you're probably compiling from git. those win machines come with msys (and flex)? not always our reviewers know how to install those tools -- Jaime Casanova 2ndQuadrant: Your PostgreSQL partner

Re: [HACKERS] Assertions in PL/PgSQL

;s a new command and works differently from RAISE. > > What about just adding a clause WHEN to the RAISE statement and use the level machinery (client_min_messages) to make it appear or not of course, this has the disadvantage that an EXCEPTION level will always happen... or you can make it a

Re: [HACKERS] Minmax indexes

sages (when autovacuum tries to vacuum this table): ERROR: could not truncate file "base/12645/16397_vm" to 2 blocks: it's only 1 blocks now CONTEXT: automatic vacuum of table "postgres.public.t1" ERROR: could not truncate file "base/12645/16397_vm" to 2 bloc

Re: [HACKERS] Minmax indexes

On Tue, Sep 17, 2013 at 8:43 AM, Thom Brown wrote: > On 17 September 2013 14:37, Jaime Casanova wrote: >> >> On Tue, Sep 17, 2013 at 3:30 AM, Thom Brown wrote: >> > On 17 September 2013 07:20, Jaime Casanova >> > wrote: >> >> >> >> On Mo

Re: [HACKERS] Minmax indexes

On Tue, Sep 17, 2013 at 3:30 AM, Thom Brown wrote: > On 17 September 2013 07:20, Jaime Casanova wrote: >> >> On Mon, Sep 16, 2013 at 3:47 AM, Thom Brown wrote: >> > On 15 September 2013 01:14, Alvaro Herrera >> > wrote: >> >> >> >>

Re: [HACKERS] Minmax indexes

lure) Another thing is this messages i got when compiling: """ mmxlog.c: In function ‘minmax_xlog_revmap_set’: mmxlog.c:161:14: warning: unused variable ‘blkno’ [-Wunused-variable] bufpage.c: In function ‘PageIndexDeleteNoCompact’: bufpage.c:1066:18: warning: ‘lastused’ may be u

Re: [HACKERS] [PATCH] bitmap indexes

nd finally, i was excercising the feature in some ways and got a crash when creating an index concurrently (attached index_failure.txt), it wasn't just a crash i couldn't start up the server again after it -- Jaime Casanova www.2ndQuadrant.com Professional PostgreSQL: Soporte 24x7

Re: [HACKERS] Assertions in PL/PgSQL

El 15/09/2013 17:13, "Marko Tiikkaja" escribió: > > On 2013-09-15 23:23, Jaime Casanova wrote: >> >> If using ASSERT as keyword is not acceptable, not that i agree but in case. >> What about using RAISE EXCEPTION WHEN (condition) > > > I think it woul

Re: [HACKERS] Assertions in PL/PgSQL

or feature, that can be implemented as extension without any lost of compatibility or lost of functionality. > > So can you redesign this without new keyword? > Hi, If using ASSERT as keyword is not acceptable, not that i agree but in case. What about using RAISE EXCEPTION WHEN (

Re: [HACKERS] Assertions in PL/PgSQL

El 14/09/2013 15:18, "Marko Tiikkaja" escribió: > > On 2013-09-14 21:55, Jaime Casanova wrote: >> >> On Sat, Sep 14, 2013 at 1:52 PM, Marko Tiikkaja wrote: >>> >>> And by "compile time" here, I mean at the time when the PL/PgSQL function &

Re: [HACKERS] Assertions in PL/PgSQL

if the second. Why not have a plpgsql.enable_assert variable? A directive you can use per function then i can keep the ASSERT and activate them by replacing the function -- Jaime Casanova www.2ndQuadrant.com Professional PostgreSQL: Soporte 24x7 y capacitación Phone: +593 4 5107566 Cell: +593 987171157

Re: [HACKERS] Differences in WHERE clause of SELECT

is any real use for that query? i understand if you ask for all customers whose names begins with 'A' but that the code begins with '1'? -- Jaime Casanova www.2ndQuadrant.com Professional PostgreSQL: Soporte 24x7 y capacitación Phone: +593 4 5107566 Cell: +593 9

Re: [HACKERS] in-catalog Extension Scripts and Control parameters (templates?)

On Sat, Jul 6, 2013 at 2:25 PM, Dimitri Fontaine wrote: > Jaime Casanova writes: >> not sure if you're wrong. but at the very least, you miss a >> heap_freetuple(oldtup) there, because get_catalog_object_by_oid() > > Well, oldtup can be either a syscache copy or a heap

Re: [HACKERS] in-catalog Extension Scripts and Control parameters (templates?)

thing is that function get_ext_ver_info() is append a new ExtensionVersionInfo which is then returned and assigned to an *evi pointer that is never used. i'm sure that evi in line 1150 is only because you need to receive the returned value. Maybe you could use "(void) get_ext_

Re: [HACKERS] in-catalog Extension Scripts and Control parameters (templates?)

On Thu, Jul 4, 2013 at 2:42 AM, Jaime Casanova wrote: > > create extension test version '123'; > CREATE EXTENSION > > postgres=# \df >List of functions > Schema | Name | Result data ty

Re: [HACKERS] in-catalog Extension Scripts and Control parameters (templates?)

On Mon, Jun 24, 2013 at 6:20 AM, Dimitri Fontaine wrote: > Jaime Casanova writes: >> just tried to build this one, but it doesn't apply cleanly anymore... >> specially the ColId_or_Sconst contruct in gram.y > > Please find attached a new version of the patch, v7, rebase

Re: [HACKERS] in-catalog Extension Scripts and Control parameters (templates?)

> I'm now working on that, setting up the documentation tool set. > > Fixed in the attached version 6 of the patch. > just tried to build this one, but it doesn't apply cleanly anymore... specially the ColId_or_Sconst contruct in gram.y -- Jaime Casanova www.2ndQuadrant

Re: [HACKERS] problem with commitfest redirection

rong. right URL is http://www.postgresql.org/message-id/CAFjNrYuh=4Vwnv=2n7cj0jjuwc4hool1epxsoflj6s19u02...@mail.gmail.com -- Jaime Casanova www.2ndQuadrant.com Professional PostgreSQL: Soporte 24x7 y capacitación Phone: +593 4 5107566 Cell: +593 987171157 -- Sent via pgsql-ha

Re: [HACKERS] Hard limit on WAL space used (because PANIC sucks)

that) had the same thing. only this was a parameter to set, and bad things happened if you forgot about it :D -- Jaime Casanova www.2ndQuadrant.com Professional PostgreSQL: Soporte 24x7 y capacitación Phone: +593 4 5107566 Cell: +593 987171157 -- Sent via pgsql-hackers mailing list

Re: [HACKERS] Planning incompatibilities for Postgres 10.0

better than reading the actual SQL. > another idea, as someone else mentioned, and i think has been discussed bedore is a function that says if the query is r-o or not... maybe even exporting the plan so we don't need to replan again... Not sure if that is possible, just hand waving...

Re: [HACKERS] Extent Locks

plus some slop. > And how do you decide the amount of that "slop"? -- Jaime Casanova www.2ndQuadrant.com Professional PostgreSQL: Soporte 24x7 y capacitación Phone: +593 4 5107566 Cell: +593 987171157 -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.

Re: [HACKERS] Extent Locks

On Tue, May 28, 2013 at 8:38 AM, Jaime Casanova wrote: > > We can also think in GUC/reloption for next_extend_blocks so formula > is needed, or of course the automated calculation that has been > proposed > s/so formula is needed/so *no* formula is needed btw, we

Re: [HACKERS] Extent Locks

nk in GUC/reloption for next_extend_blocks so formula is needed, or of course the automated calculation that has been proposed -- Jaime Casanova www.2ndQuadrant.com Professional PostgreSQL: Soporte 24x7 y capacitación Phone: +593 4 5107566 Cell: +593 987171157 -- Sent via pgsql-hack

  1   2   3   4   5   6   7   8   9   >