On Sun, Feb 6, 2011 at 2:12 PM, Jaime Casanova wrote:
> On Tue, Feb 1, 2011 at 11:32 PM, Joachim Wieland wrote:
>> On Sun, Jan 30, 2011 at 5:26 PM, Robert Haas wrote:
>>> The parallel pg_dump portion of this patch (i.e. the still-uncommitted
>>> part) no lon
On Mon, Feb 7, 2011 at 10:59 PM, Robert Haas wrote:
> On Fri, Feb 4, 2011 at 9:15 PM, Jaime Casanova wrote:
>> ok, i will see you're reviewed version later today
>
> This patch is still marked as "Needs Review" in the CommitFest
> application, but I'm th
his, until now the only issue i have found
is that if i set allow_standalone_primary to off and there isn't a
standby connected i need to stop the server with -m immediate which is
at least surprising
--
Jaime Casanova www.2ndQuadrant.com
Professional PostgreSQL: Soporte y capacitación
FY. Perhaps
>> that could be used?
>
> Well, those are going to require work to notify someone externally, like
> send an email alert.
>
although, that seems the work for a monitor tool.
--
Jaime Casanova www.2ndQuadrant.com
Professional PostgreSQL: Soporte y capacitación
some data then you should disable synchronous_replication
as well as synchronous_commit... maybe sending a message to the log
when you detect the conflicting situation.
--
Jaime Casanova www.2ndQuadrant.com
Professional PostgreSQL: Soporte y capacitación de PostgreSQL
--
Sent via pgsq
On Sun, Feb 20, 2011 at 7:20 AM, Florian Pflug wrote:
> On Feb20, 2011, at 08:12 , Jaime Casanova wrote:
>> considering that synchronous_replication to on means that we *want*
>> durability, and that synchronous_commit to off means we don't *care*
>> about durability. T
c->lwWaitLink;
}
if (proc->lwWaitLink == NULL) /* At tail */
{
! Assert(proc != MyProc);
/* Remove ourselves from tail of queue */
Assert(queue->tail == MyProc);
will always be the synch standby until it's removed from the list
or phisically.
the other comment in the doc should be removed
--
Jaime Casanova www.2ndQuadrant.com
Professional PostgreSQL: Soporte y capacitación de PostgreSQL
--
Sent via pgsql-hackers mailing list (pgsql-hackers@p
; cases.
i guess, we can put a new column in pg_stat_replication stating the
type of the replication (synch or asynch).
but that is surely a different patch...
--
Jaime Casanova www.2ndQuadrant.com
Professional PostgreSQL: Soporte y capacitación de PostgreSQL
--
Sent via pgsql-hacker
transaction unexpectedly would wait for replication
> infinitely.
>
actually i think we should reject such standby as a synch standby, and
look for another one in the synchronous_standby_names list
--
Jaime Casanova www.2ndQuadrant.com
Professional PostgreSQL: Soporte y capacitación
ling right now to test again and see the effects, Robert
maybe you can test your failure case again? i'm really sure it's
related to this...
--
Jaime Casanova www.2ndQuadrant.com
Professional PostgreSQL: Soporte y capacitación de PostgreSQL
--
Sent via pgsql-hackers mailing l
is that Simon fixed them in one day...
And for the open items, most of them are definitions about the behaviour...
--
Jaime Casanova www.2ndQuadrant.com
Professional PostgreSQL: Soporte y capacitación de PostgreSQL
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To m
om this so i expect he will post a patch
soon, meanwhile i'm following his repo and testing and seems i'm not
the only one because Yeb Havinga has added two columns in
pg_stat_replication to know which standby is the synch standby and
which ones are potential synch standbys
--
Jaim
them to be async, 2) also * will give priority 1 to all standbys so it
doesn't seem like a very useful out-of-the-box configuration, better
to make the dba to write the standby names in the order they want
--
Jaime Casanova www.2ndQuadrant.com
Professional PostgreSQL: Soporte y capacitación d
e is
> required.
>
It's not better to remove the code to manage * in synchronous_standby_names?
Once we do that there is no chance of having 2 standbys with the same
priority.
After all, most of the times the dba will need to change the * for a real
list of names anyway. At least in IMHO
--
Jaime Casanovawww.2ndQuadrant.com
n't
> 3) speed is comparable to v17 :-)
>
yeah... it's a lot better than before, good work Simon :)
--
Jaime Casanova www.2ndQuadrant.com
Professional PostgreSQL: Soporte y capacitación de PostgreSQL
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make
o introduce something like "pg_ctl standalone" command?
>
> Well, there is one way to end the wait: shutdown, or use
> pg_terminate_backend().
>
I disconnected all standbys so the master keeps waiting on commit. Then i
shutdown the master with immediate and got a cras
for sync rep.
+1 for Fujii's proposal
--
Jaime Casanova www.2ndQuadrant.com
Professional PostgreSQL: Soporte y capacitación de PostgreSQL
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
elegant :(
any idea what happens to this part of the history?
--
Jaime Casanova www.2ndQuadrant.com
Professional PostgreSQL: Soporte y capacitación de PostgreSQL
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
king the info to git...
that -S option looks like a life saver, thanks!
--
Jaime Casanova www.2ndQuadrant.com
Professional PostgreSQL: Soporte y capacitación de PostgreSQL
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
htt
f you know the server was a standby and pg_is_in_recovery() returns
false then it was promoted.
is that what you want to know? or i misunderstood you?
--
Jaime Casanova www.2ndQuadrant.com
Professional PostgreSQL: Soporte y capacitación de PostgreSQL
--
Sent via pgsql-hackers mailing list (p
ge?
Also the directory in which the pg_hba.conf is is only
visible/writable for the database cluster owner and the system
administrator, so that means you're allowing your user to connect to
the server as one of those users? or is windows uncapable of enforce
those restrictions?
--
J
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
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
;
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
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
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
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
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
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
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
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
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
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
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
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-
'm
>> good with not changing things.
>
> Yeah, that's because I was responding to the suggestion that 5 of our
> lists should be collapsed into 'general' as the One Uber-List.
>
i think not all should be collapsed but at least -novice, IMHO
--
Jaime Casanova
On Thu, May 13, 2010 at 11:00 PM, Tom Lane wrote:
> Jaime Casanova writes:
>> On Thu, May 13, 2010 at 10:52 PM, Tom Lane wrote:
>>> Actually, the lexer translates N'foo' to NCHAR 'foo' and then the
>>> grammar treats that just like CHAR '
On Mon, Jun 7, 2010 at 2:23 AM, Peter Eisentraut wrote:
>
> The N'' syntax is in the SQL standard,
>
I didn't know that, do you know what paragraph is it? i can't find it
--
Jaime Casanova www.2ndQuadrant.com
Soporte y capacitación de PostgreSQL
--
Sent v
On Mon, Jan 18, 2010 at 3:55 AM, Takahiro Itagaki
wrote:
>
> Robert Haas wrote:
>
>> A couple of preliminary comments on this:
>
> Thanks.
> The attached is rebased on HEAD, with additional documentation.
>
This one, doesn't apply to head anymore... please update
sy with other things... i will make a complete
review in next days...
--
Jaime Casanova www.2ndQuadrant.com
Soporte y capacitación de PostgreSQL
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
y. Nothing else.
>
so, merging this with the autovacuum will drop our hopes of having a
time based autovacuum? not that i'm working on that nor i was thinking
on working on that... just asking to know what the implications are,
and what the future improves could be if we go this route
--
Jai
ertised, pass regression tests, and all
tests i could think of...
haven't looked the code at much detail but seems ok, to me at least...
--
Jaime Casanova www.2ndQuadrant.com
Soporte y capacitación de PostgreSQL
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
T
On Fri, Jul 23, 2010 at 10:05 AM, Jaime Casanova wrote:
> On Thu, Jun 10, 2010 at 3:39 PM, Robert Haas wrote:
>>
>>
>> I believe that this patch will clear away one major obstacle to
>> implementing global temporary and unlogged tables: it enables us to be
>> sur
On Sun, Jul 25, 2010 at 4:32 PM, Robert Haas wrote:
> On Sun, Jul 25, 2010 at 2:37 AM, Jaime Casanova wrote:
>> but i have a few questions, maybe is right what you did i only want to
>> understand it:
>> - you added this in include/storage/smgr.h, so why is safe to assume
&
ate locale "es_EC.utf8""
(of course, that last part was me messing the things up, but it show
we shouldn't be using a file locales.txt, i think)
i can attach a collate to a domain but i can't see where are we
storing that info (actually it says it's not collatable):
--
On Fri, Aug 6, 2010 at 12:50 PM, Robert Haas wrote:
>
> Just "DROP TABLE
> pg_temp_2.foo" or whatever and away you go.
>
wow! that's true... and certainly a bug...
we shouldn't allow any session to drop other session's temp tables, or
is there a reason for
)
there's something we can/need to do about it?
I can make a list if anyone is interested showing what files are still
copyrighted to something different to 'PostgreSQL Global Development
Group'
--
Jaime Casanova www.2ndQuadrant.com
Soporte y capacitación de PostgreSQL
--
2010 at 11:32 AM, Peter Eisentraut wrote:
> On mån, 2010-08-02 at 01:43 -0500, Jaime Casanova wrote:
>> nowadays, CREATE DATABASE has a lc_collate clause. is the new collate
>> clause similar as the lc_collate?
>> i mean, is lc_collate what we will use as a default?
>
On Mon, Aug 16, 2010 at 10:56 PM, Peter Eisentraut wrote:
> On lör, 2010-08-14 at 02:05 -0500, Jaime Casanova wrote:
>
>> BTW, why the double quotes?
>
> Because the name contains upper case letters?
>
why everything seems so obvious once someone else state it? :)
>>
On Wed, Aug 18, 2010 at 11:29 AM, Peter Eisentraut wrote:
> On tis, 2010-08-17 at 01:16 -0500, Jaime Casanova wrote:
>> >> creating collations ...FATAL: invalid byte sequence for encoding
>> >> "UTF8": 0xe56c09
>> >> CONTEXT: COPY
only in version 8 so Oracle should have more features...
no that i follow that reasoning but...
--
Jaime Casanova www.2ndQuadrant.com
Soporte y capacitación de PostgreSQL
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://
On Fri, Aug 20, 2010 at 4:48 PM, Greg Stark wrote:
> On Fri, Aug 20, 2010 at 10:41 PM, Jaime Casanova
> wrote:
>> Look at other DBMSes:
>> Oracle: 8i, 9i, 10g, 11g
>> Informix 9, 10, 11
>> MS SQL Server 7, 2000, 2005, 2008
>>
>> note the lack of dotes (
t of this seems to be (based on the examples on the page,
haven't read the patch) scripting functionality but now that we have
DO, is really a need for that?
i'm not really sure if we can do what the same as your example using
DO but i'm really dubious about the usefullness
right solution is move towards make a normal
table unlogged and viceversa... probably that's harder to do but we
will have better control and less odd heuristics
--
Jaime Casanova www.2ndQuadrant.com
Professional PostgreSQL: Soporte 24x7 y capacitación
--
Sent via pgsql-hackers ma
e low you need them. I say,
create a subdirectory.
"""
--
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
pg_dump -Fc -Osx and use pg_restore -l to list
objects. then you can sort and compare objects and then a script that
compare schema of objects extracting them with -P, -T or -t
--
Jaime Casanova www.2ndQuadrant.com
Professional PostgreSQL: Soporte 24x7 y capacitación
--
Sent via pgsql-ha
On Tue, Aug 30, 2011 at 3:14 PM, Joe Abbate wrote:
> Hola Jaime,
>
> On 08/30/2011 03:24 PM, Jaime Casanova wrote:
>>
>> what about using pg_dump -Fc -Osx and use pg_restore -l to list
>> objects. then you can sort and compare objects and then a script that
>> com
fer values {on, off, verbose}
where "on" will log just the same as now
--
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
s work, except with an absolute number rather than
> relative.
cool! just a question, shouldn't we clean the value after the base
backup has finished?
--
Jaime Casanova www.2ndQuadrant.com
Professional PostgreSQL: Soporte 24x7 y capacitación
--
Sent via pgsql-hackers mailing list
pg_current_timeline(), pg_start_backup());".
>
we can do "SELECT pg_xlogfile_name(pg_start_backup())" now, so how is
that different?
> Furthermore, in the same way, we can get the backup end WAL file name or
> current WAL file name from pg_stop_backup() or pg_current_x
Last I checked (it has been a few years) that was at best, a hack. I
> remember either I or David Fetter? Writing about some issues with it on list
> but it was a long time ago.
>
last time i tried it (last year), it seems broken because i couldn't
log in with any user anymo
, and be able to have the same "userid" for different
> databases, using different settings...
>
why "before" login? in 9.0+ you can use ALTER ROLE ... IN DATABASE,
doesn't it help?
pre 9.0 need the db_user_namespace GUC for that, though
--
Jaime Casanova w
r each meeting either on -hackers or pgsql-sql.
>
Well Susanne said that the drafts are not public information so maybe
the things that *could* end up in a draft shouldn't be either, if so i
agree with the idea of creating a private list for that
--
Jaime Casanova www.2ndQuadrant.com
to 1 but in windows and
solaris it actually defaults to 0
>> (I still think we should get rid of the commented-out settings
>> altogether, but that's another argument...)
>
> That's another reason not to expend work here --- it still seems
> fairly likely that that might hap
#x27;t read all the code in the detail but seems fine to me
in other things:
do we need to include src/bin/pg_basebackup/.gitignore in the patch?
--
Jaime Casanova www.2ndQuadrant.com
Professional PostgreSQL: Soporte 24x7 y capacitación
--
Sent via pgsql-hackers mailing list (
On Wed, Sep 28, 2011 at 1:38 AM, Jaime Casanova wrote:
> On Tue, Aug 16, 2011 at 9:32 AM, Magnus Hagander wrote:
>> Here's an updated version of pg_receivexlog, that should now actually
>> work (it previously failed miserably when a replication record crossed
>> a WAL
eceivexlog to this file,
> yes - in head it just contains pg_basebackup.
>
your patch includes a modification in the file
src/bin/pg_basebackup/.gitignore, maybe i'm just being annoying
besides is a simple change... just forget that...
--
Jaime Casanova www.2ndQuadrant.com
Profes
strictions have that effect ;)
--
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
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
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
;
> Could we pass a parameter from the client indicating to the master
> that it refuses to be a sync slave? An optional keyword to the
> START_REPLICATION command, perhaps?
>
can't you execute "set synchronous_commit to off/local" for this connection?
--
Jaime Casanova
e are going to create the "state" column let's do it now and
change current_query for last_query (so last query can be running, or
it was the last before enter in idle state)
--
Jaime Casanova www.2ndQuadrant.com
Professional PostgreSQL: Soporte 24x7 y capacitación
--
Se
he right
buffer access strategy so it's using a ring buffer now
--
Jaime Casanova www.2ndQuadrant.com
Professional PostgreSQL: Soporte 24x7 y capacitación
diff --git a/contrib/pageinspect/btreefuncs.c b/contrib/pageinspect/btreefuncs.c
new file mode 100644
index dbb2158..8be2
ss.ntt.co.jp
not sure what happens after that.
--
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
to 1.1.
>
good point... fixed that...
a question i have is: are we supposed to let the old script (1.0) around?
--
Jaime Casanova www.2ndQuadrant.com
Professional PostgreSQL: Soporte 24x7 y capacitación
diff --git a/contrib/pageinspect/Makefile b/contrib/pageinspect/Makefile
new file mode
Hi,
This patch doesn't apply cleanly to head now... can you send a new
version against head?
about the patch itself. i don't like the fact that now the normal case
needs to include the word TABLE. IMHO, it should be optional and if
ommited TABLE should be assumed
--
Jaime Cas
> TOAST Table at its place
> ALTER TABLE ... SET TOAST TABLESPACE => keeps Table at its place &
> moves associated TOAST Table
>
oh! i didn't test the patch just read it... and maybe i misunderstood,
will see it again.
--
Jaime Casanova www.2ndQuadrant.com
Professiona
BLE SET TABLE TABLESPACE
ALTER TABLE SET TOAST TABLESPACE
why not also support ALTER TABLE SET INDEX TABLESPACE which should
have the same behaviour as ALTER INDEX SET TABLESPACE... just an idea,
and of course not necessary for this patch
--
Jaime Casanova www.2ndQuadrant.com
Professional Postgre
ng column to the new value of the referenced column,
respectively.
"""
so, that is what i will expect
--
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
lly at fault?
>
i can't find anything about this in the standard, so i guess even if
the standard allows us to turn checks off. ours is not standard syntax
so, IMHO, it should be only in ALTER TABLE.
--
Jaime Casanova www.2ndQuadrant.com
Professional PostgreSQL: Soporte 24x7 y cap
hat objection, with much less
> work than Robert suggests, if we just made the message be a WARNING not
> an ERROR. I think that'd do just as well in terms of what the message
> could usefully accomplish, ie, steer people away from doing things that
> won't work. Still not su
eds adjustment for the
rangetypes regress test
--
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
s in the supported objects and treat them as normal
pages...
or there is something i'm missing?
--
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
opinion about this? maybe i can make a patch for that if there is
consensus that it could be good for symettry
--
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
On Mon, Dec 12, 2011 at 10:54 AM, Julien Tachoires wrote:
> Hi,
>
> 2011/12/10 Jaime Casanova :
>> On Mon, Nov 28, 2011 at 1:32 PM, Julien Tachoires wrote:
>>
>>>> 2) after CLUSTER the index of the toast table gets moved to the same
>>>> tablespace
and saw some regression with normal pgbench runs, but it wasn't
much... so i was trying to found out some queries that show benefit
now that we have it, that will be a lot more easier
--
Jaime Casanova www.2ndQuadrant.com
Professional PostgreSQL: Soporte 24x7 y capacitación
--
Sent
nt explaining
those? more important it's seems obvious something broke that, unless
i misunderstood something which is completely possible, and that the
way is do it it will broke again in the future if the header change
--
Jaime Casanova www.2ndQuadrant.com
Professional PostgreSQL: Sop
?
--
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
e2c2c2e8b1df7dfdb01e7e6f6191a569ce3c3195 to "Improve planner's
handling of duplicated index column expressions", so this commit broke
something or the count is wrong in the expected result
--
Jaime Casanova www.2ndQuadrant.com
Professional PostgreSQL: Soporte 24x7 y capacit
On Thu, Jan 12, 2012 at 1:59 PM, Tom Lane wrote:
> Jaime Casanova writes:
>> the query where the regression fails is:
>
>> SELECT count(*) FROM dupindexcols
>> WHERE f1 > 'LX' and id < 1000 and f1 ~<~ 'YX';
>
>> my first theory was
ion_free_space() patch to accept toast tables and other kind
of indexes and add it to the commitfest unless someone says that my
math is wrong and somehow there is a more accurate way of getting the
free space (which is entirely possible)
--
Jaime Casanova www.2ndQuadrant.com
Professiona
unity for anyone to point my error if any
> - relation_free_space() belongs in the pgstattuple extension, because its role
> is cheaper access to a single pgstattuple() metric.
>
oh! right! so, what about just fixing the free_percent that
pgstattuple is providing
--
Jaime Casanova w
nstead of disconnect_and_exit() and that is probably a
typo too
--
Jaime Casanova www.2ndQuadrant.com
Professional PostgreSQL: Soporte 24x7 y capacitación
diff --git a/src/bin/pg_basebackup/pg_basebackup.c b/src/bin/pg_basebackup/pg_basebackup.c
new file mode 100644
index 4007680..22d906a
next cycle?
do we consider this as a useful thing?
--
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
almost complete since last CF and seems
something we want... i made some performance test that didn't give me
good results last time but didn't show them and wasn't able to
reproduce so maybe it was something in my machine...
so, i would say add it and if the CF manager d
actly that or am I missing your point?
>
not really.
if you have 12 cores and you say -j 12 you would have 1 process per
core, with Susanne's suggestion, AFAIUI, you can say -j 12
--shared-cores=6... so you would only use 6 cores of the 12 and have 2
processes per core
--
rable difference
between pgstattuple and relation_free_space()
--
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
w unsafe to call OpenTemporaryFile outside a transaction.
ok, you are right... what do you suggest?
maybe move the GetTempTablespace function to somewhere in src/backend/utils?
--
regards,
Jaime Casanova
"Programming today is a race between software engineers striving to
build bigger and better idi
On 3/17/07, Tom Lane <[EMAIL PROTECTED]> wrote:
"Jaime Casanova" <[EMAIL PROTECTED]> writes:
> On 3/5/07, Tom Lane <[EMAIL PROTECTED]> wrote:
>> In the second place, it's a serious violation of what little modularity
>> and layering we have f
301 - 400 of 850 matches
Mail list logo
