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
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
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
> 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
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
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
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
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
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
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
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)
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
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
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
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
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
(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,
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
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
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ó
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
_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
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
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
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
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
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
&
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 (
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
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
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
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:
>> >>
>> >>
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
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
;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
#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
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
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
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
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
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
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
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
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
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
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
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
_DELETED and the WAL record type were left in place because of
> that.
I guess it was an oversight, because GistPageSetDeleted() is being
used in gistRedoPageDeleteRecord() and GistPageIsDeleted() in a few
other places
--
Jaime Casanova www.2ndQuadrant.com
Professional Postgr
On Wed, Jan 18, 2012 at 7:01 PM, Noah Misch wrote:
> On Wed, Jan 18, 2012 at 09:46:20AM -0500, Jaime Casanova wrote:
>>
>> ignoring all non-leaf pages still gives a considerable difference
>> between pgstattuple and relation_free_space()
>
> pgstattuple() counts the
e, please choose another one using the unused_oids
script (3150)
- pg_stat_reset() doesn't reset deadlock counter (see
pgstat_recv_resetcounter())
everything else seems fine to me
--
Jaime Casanova www.2ndQuadrant.com
Professional PostgreSQL: Soporte 24x7 y capacitación
--
Sent via
r all kind of indexes (problem is that this is
inconsistent with the fact that pageinspect only manages btree indexes
for everything else)
--
Jaime Casanova www.2ndQuadrant.com
Professional PostgreSQL: Soporte 24x7 y capacitación
diff --git a/contrib/pageinspect/Makefile b/contrib/
On Wed, Feb 1, 2012 at 9:18 PM, Fujii Masao wrote:
>>>
>>> --On 15. Januar 2012 02:50:00 -0500 Jaime Casanova
>>> wrote:
>>>
>>>> Attached is a patch thats implements a pg_stat_recovery view that
>>>> keeps counters about p
nch scale 20 (average of 3 runs, -T 300 clients
=1, except on second run)
-scale 20
== simple ==
head 19.890278
cache 19.536342
== simple (10 clients) ==
head 40.864455
cache 44.457357
== extended ==
head 21.372751
cache 19.992955
== prepared ==
head 19.543434
cache 20.226981
== select only ==
hea
ter to the relation_free_space()
function, it mimics the way analyze choose the blocks to read and is
faster than plain relation_free_space() but of course could be inexact
if the pages that we don't read are the ones with more free space
--
Jaime Casanova www.2ndQuadrant.com
Profes
al_record_type
(xl_info) being a number is not that clear
--
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
R EACH { ROW | STATEMENT } ]
[ WHEN]
::=
| BEGIN ATOMIC { }... END
--
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 subscr
ms to work fine.
What i don't like about it is that spgnull.c actually call GIN
functions and even uses GIN flags. Don't know how bad it is, but IMO
there is a module violation here.
--
Jaime Casanova www.2ndQuadrant.com
Professional PostgreSQL: Soporte 24x7 y capacitación
-
On Sat, Feb 4, 2012 at 5:40 AM, Marti Raudsepp wrote:
> On Sat, Feb 4, 2012 at 09:49, Jaime Casanova wrote:
>> i little review...
>
> Thanks! By the way, you should update to the v7 patch.
>
just tried it and it fail when initializing on make check
"""
cre
entry, everything works fine.
The only thing is that i don't see a reason for these includes in
src/backend/utils/adt/misc.c:
+ #include "nodes/nodeFuncs.h"
+ #include "utils/lsyscache.h"
--
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
for
> goverment (Orcale) - jobs are the core gears for data flow between many
> systems and other goverment bureaus.
>
me too, and we solve it with cron
--
Jaime Casanova www.2ndQuadrant.com
Professional PostgreSQL: Soporte 24x7 y capacitación
--
Sent via pgsql-hac
one crashed, or because it's shutting down).
>
+1
--
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
UE),
+errmsg("ending block number "
INT64_FORMAT " exceeds number of
blocks in relation " INT64_FORMAT, last_block, nblocks)));
+ }
--
Jaime Casanova www.2ndQuadrant.com
Professional PostgreSQL: Soporte 24x7 y capacitació
that feature and resubmit easily
>> enough, will turn that around soon.
>
> This change seems plenty small enough to slip in even at this late
> date, but I guess we're lacking a new version of the patch.
>
Sorry, here's the patch rebased and with the suggestion fr
On Fri, Mar 9, 2012 at 12:46 AM, Jaime Casanova wrote:
> On Thu, Mar 8, 2012 at 8:25 AM, Robert Haas wrote:
>> On Sun, Feb 12, 2012 at 9:19 PM, Greg Smith wrote:
>>> The smaller step of automatically stripping the specified suffix from the
>>> input file name, when it
On Wed, Feb 22, 2012 at 12:27 AM, Noah Misch wrote:
> On Tue, Feb 14, 2012 at 02:04:26AM -0500, Jaime Casanova wrote:
>>
>> 1) pgstattuple-gin_spgist.patch
>> This first patch adds gin and spgist support to pgstattuple, also
>> makes pgstattuple use a ring buffer whe
On Fri, Mar 9, 2012 at 9:07 AM, Robert Haas wrote:
> On Fri, Mar 9, 2012 at 12:47 AM, Jaime Casanova wrote:
>>> Sorry, here's the patch rebased and with the suggestion from Alex.
>>> Which reminds me, I never thank him for the review (shame on me) :D
>>
>>
On Sat, Mar 10, 2012 at 2:38 PM, Jaime Casanova wrote:
> On Fri, Mar 9, 2012 at 9:07 AM, Robert Haas wrote:
>> On Fri, Mar 9, 2012 at 12:47 AM, Jaime Casanova
>> wrote:
>>>> Sorry, here's the patch rebased and with the suggestion from Alex.
>>>>
nd
them to be applied equally to all partitions.
"""
--
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
is no reason for" you can
add a parentesis saying "more info in "
--
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://w
; You left the
> bstrategy variable non-static, but that didn't seem important enough to
> justify another round trip.
>
ah! i forgot that...
--
Jaime Casanova www.2ndQuadrant.com
Professional PostgreSQL: Soporte 24x7 y capacitación
--
Sent via pgsql-hackers mailing list (
Hi,
Has anyone ever complained about the inconsistency (at least it seems
that to me) of using INHERITS in CREATE TABLE and INHERIT in ALTER
TABLE?
Anyone, besides me, think we should fix that? Maybe support both
version in both commands or choosing one using it everywhere?
--
Jaime Casanova
On Sat, Mar 17, 2012 at 2:16 PM, Atri Sharma wrote:
> Hi Dave,
>
> I believe,with the ALTER command,we plan to give the user power to modify
> ordering . Don’t we?
>
And how is that different from a view that orders the columns as the
user wishes?
--
Jaime Casanova www.
chives.postgresql.org/message-id/cahgqgwhwqjgeksmp2oteru8p0sj6x7ypqyh5qqeqcbqsxaa...@mail.gmail.com
--
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://w
are fired but i
tried on 8.4 to 9.1 and all of these have the same behaviour
attached is a simple contained test of this
PS: i'm hoping this is just me needed to sleep
--
Jaime Casanova www.2ndQuadrant.com
Professional PostgreSQL: Soporte 24x7 y capacitación
drop database if exists t
On Wed, Mar 28, 2012 at 1:21 AM, Jaime Casanova wrote:
> Hi,
>
> i was trying to create triggers that redirect INSERT/UPDATE/DELETE
> actions from parent to childs, but found that UPDATE/DELETE doesn't
> get redirected. Actually, the triggers BEFORE UPDATE and BEFORE DELETE
, but in one of its child tables. So any triggers on
> the child table would fire, but triggers on the parent table will not.
>
ah! and of course that makes a lot of sense...
how embarrasing! :(
--
Jaime Casanova www.2ndQuadrant.com
Professional PostgreSQL: Soporte 24x7 y capacitació
7;m not sure i want to contor things for that...
so, just forget my last mail about that... your refactor is just fine for me
--
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
I am still kind of busy with my university final year project. I shall
> not have time to work on updating the patch until this semester finishes
> which is December. I will work on then.
Hi,
Should we expect an updated patch for next commitfest?
--
Jaime Casanova www.2ndQuadr
ced during the pgcon closing session -
> Jeff Davis, Stephen frost, fujii masao and Noah misch.
>
Congratulations for you guys...
--
Jaime Casanova www.2ndQuadrant.com
Professional PostgreSQL: Soporte 24x7 y capacitación
Phone: +593 4 5107566 Cell: +593 987171157
--
Sent via
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
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
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.
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...
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
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
> 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
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
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
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_
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
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
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
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
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
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
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
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
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
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()
>
> 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
1 - 100 of 850 matches
Mail list logo
