On Mon, Apr 12, 2010 at 1:23 AM, Jaime Casanova
wrote:
>
> another point, what happened with this:
> http://archives.postgresql.org/message-id/1229549172.4793.105.ca...@ebony.2ndquadrant?
> Obviously we still have the problem with hash indexes, and in that
> thread Tom advice was j
On Tue, Apr 13, 2010 at 11:06 AM, Heikki Linnakangas
wrote:
> Jaime Casanova wrote:
>>
>> i will read it on the morning and the thread where it is, something
>> that seems strange to me is that the patch touch twophase.c and
>> twophase.h, why?
>
> When you
On Sat, Apr 10, 2010 at 12:23 AM, Jaime Casanova
wrote:
> On Fri, Apr 9, 2010 at 3:39 PM, Jaime Casanova
> wrote:
>>
>
> i think "make standbycheck" needs a little more work, why it isn't
> accesible from top of source dir?
>
what i want to do.
1) make st
as anything.
>
> Although on further reflection, part of me feels like it might be even
> simpler and clearer to simply say:
>
> connection not authorized
>
+1
--
Atentamente,
Jaime Casanova
Soporte y capacitación de PostgreSQL
Asesoría y desarrollo de sistemas
Guayaquil
or more...
someone can confirm the lock contention theory? this should be
noticeable at checkpoint time right?
--
Atentamente,
Jaime Casanova
Soporte y capacitación de PostgreSQL
Asesoría y desarrollo de sistemas
Guayaquil - Ecuador
Cel. +59387171157
--
Sent via pgsql-hackers mailing list (pgsql
them is because somebody else might have 'em open, so it
> mightn't be necessary for temp rels.
>
what happens if the backend crash and obviously doesn't remove the
file associated with temp rels?
--
Atentamente,
Jaime Casanova
Soporte y capacitación de PostgreSQL
Asesoría y desarr
Hi,
while TFM says that we can use EXECUTE 'select ' INTO instead of the
non implemented EXECUTE 'select ... into ', the message in plpgsql
fails to say the same thing... seems like a HINT to me
--
Atentamente,
Jaime Casanova
Soporte y capacitación de PostgreSQL
Ases
On Wed, Apr 14, 2010 at 9:16 AM, Jaime Casanova
wrote:
> On Sat, Apr 10, 2010 at 12:23 AM, Jaime Casanova
> wrote:
>> On Fri, Apr 9, 2010 at 3:39 PM, Jaime Casanova
>> wrote:
>>>
>>
>> i think "make standbycheck" needs a little more work,
erything that we need to...
maybe just a new set of tests? maybe i just should make the hs_* tests
use regression's database tables intead of the ones it is using?
--
Atentamente,
Jaime Casanova
Soporte y capacitación de PostgreSQL
Asesoría y desarrollo de sistemas
Guayaquil - Ecuador
C
ave a URL?
>
i guess he is refering to the plpgsql's PERFORM statement, which of
course he can't use outside a plpgsql function...
mmm... well, IIRC, in 9.0 he will be able to do DO $$ PERFORM * FROM
tabla; $$ LANGUAGE plpgsql;
but i think DO is not an EXPLAINing statement
--
A
e the query.
>>
>> I would use EXPLAIN ANALYZE SELECT ...
>
> There's some overhead to that, of course.
>
he could see the "actual time" in the very first row of the EXPLAIN
ANALYZE... isn't that a value that is more close to what the OP is
looking for?
--
At
we aren't able to
use hash indexes on the slave so we can advice to disable those
indexes there
the only problem is that seems like we can't put
"plantuner.forbid_index='a_hash_index'" on postgresql.conf ala
auto_explain, that could make this better
--
Atentamente
1000C" from archive
PANIC: btree_redo: unknown op code 208
CONTEXT: xlog redo UNKNOWN
LOG: startup process (PID 9264) was terminated by signal 6: Aborted
LOG: terminating any other active server processes
"""
--
Atentamente,
Jaime Casanova
Soporte y capacitació
Hi,
COPY is not working on latest HEAD?
"""
regression=# select * from a;
aa
32
56
(2 rows)
regression=# COPY a TO '/tmp/copy_test';
COPY 0
"""
--
Atentamente,
Jaime Casanova
Soporte y capacitación de PostgreSQL
Asesoría y desarrollo de sistem
2010/4/30 Jaime Casanova :
> Hi,
>
> COPY is not working on latest HEAD?
> """
> regression=# select * from a;
> aa
>
> 32
> 56
> (2 rows)
>
> regression=# COPY a TO '/tmp/copy_test';
> COPY 0
> """
>
ah!
On Fri, Apr 30, 2010 at 12:56 AM, Takahiro Itagaki
wrote:
>
> Jaime Casanova wrote:
>
>> COPY is not working on latest HEAD?
>> """
>> regression=# select * from a;
>> aa
>>
>> 32
>> 56
>> (2 rows)
>>
>>
On Fri, Apr 30, 2010 at 1:13 AM, Takahiro Itagaki
wrote:
>
> Jaime Casanova wrote:
>
>> ah! this is because COPY doesn't follow inherited tables... should it?
>
> Yes. You can use "COPY (SELECT * FROM a) TO " instead to copy all tuples.
>
> http://de
On Fri, Apr 30, 2010 at 12:03 AM, Tom Lane wrote:
> Jaime Casanova writes:
>> i was trying recent HS and get this when trying to start the standby,
>
>> TRAP: FailedAssertion("!(( (metabuffer) != 0 && (metabuffer) >=
>> -NLocBuffer && (metabuffer)
On Sat, May 1, 2010 at 7:22 AM, Simon Riggs wrote:
> On Mon, 2010-04-26 at 02:45 -0500, Jaime Casanova wrote:
>> On Mon, Apr 26, 2010 at 2:32 AM, Heikki Linnakangas
>> wrote:
>> >
>> > How many of the tests in the regular regression suite do anything useful
>&
nside that trigger will look at the entire set of tables
(as long as you don't use FROM ONLY)
also could be useful to put an index (even a PK) on every child to
ensure uniqueness and make the SELECT more efficient, and of course a
check constraint in every child emulating a partition key
s actually works, is that fine? i
know, we can use E'' strings but N'' ones are no where documented, so
can i rely on those or i have to change those strings?
"""
create table t1_nvarchar(col1 text);
insert into t1_nvarchar values (N'texto');
"
any effect on
> encoding behavior. I think this is something Tom Lockhart put in ten or
> so years back, and never got as far as making it actually do anything
> helpful.
>
so, the N'' syntax is fine and i don't need to hunt them as a migration step?
--
Jaime Casanova
On Thu, May 13, 2010 at 10:13 PM, Takahiro Itagaki
wrote:
>
> Jaime Casanova wrote:
>
>> i migrate a ms sql server database to postgres and was trying some
>> queries from the application to find if everything works right...
>> when i was looking to those queries i fou
e thread and
"mark as read" everything else
--
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
excessive to me, IMHO
--
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
On Sat, May 15, 2010 at 10:16 PM, Tom Lane wrote:
> Jaime Casanova writes:
>> On Sat, May 15, 2010 at 8:51 PM, Tom Lane wrote:
>>> Is it reasonable to fix this now, and if so should I bump catversion
>>> or leave it alone? My own preference is to fix it in
On Sat, May 15, 2010 at 10:21 PM, Tom Lane wrote:
> Jaime Casanova writes:
>> On Sat, May 15, 2010 at 10:16 PM, Tom Lane wrote:
>>> Jaime Casanova writes:
>>>> On Sat, May 15, 2010 at 8:51 PM, Tom Lane wrote:
>>>> Is it reasonable to fix this now,
ecision as $$
select random() * $1;
$$ language sql immutable;
create index idx on t1(f1(col1));
"""
then, welcome to the club... there were various conversations on this same topic
--
Jaime Casanova www.2ndQuadrant.com
Soporte y capacitación de PostgreSQL
--
Sent
little later than planned, but as
> promised almost exactly one year ago).
maybe i'm not understanding but this will be able to build specific
branches so we can have some experimental code running in buildfarm?
--
Jaime Casanova www.2ndQuadrant.com
Soporte y capacitación de PostgreSQL
DML against MV, I expect that triggers should work too
>
no, if you don't propagate then you don't have a view of the tables
the MV comes from...
error if you'll not implement propagation now
--
Jaime Casanova www.2ndQuadrant.com
Soporte y capacitación de PostgreSQL
--
On Tue, Nov 29, 2011 at 10:12 PM, Robert Haas wrote:
> On Tue, Nov 29, 2011 at 11:11 AM, Jaime Casanova
> wrote:
>> On Tue, Nov 29, 2011 at 10:42 AM, Tom Lane wrote:
>>> Bruce Momjian writes:
>>>> Tom Lane wrote:
>>>>> Robert Haas writes:
>&
es in HS" but is not transparent (unless you
come from oracle, most db's uses local temp tables just as postgres
does) and certainly is not an ideal solution... FWIW, no one that i
know will want to do those "fixes" in their app.
--
Jaime Casanova www.2ndQuadrant.com
Pr
commitfest
(https://commitfest.postgresql.org/action/commitfest_view?id=14) that
will start on june 15. is difficult to know if something we haven't
seen is acceptable or not (please add some description about the way
you did it)
if the patch is still not ready, then start explaining the design you
are goi
REATE SEQUENCE also
create an entry in pg_type. there is any reason for 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:
On Thu, Jun 7, 2012 at 5:15 PM, Tom Lane wrote:
> Please join me in welcoming him aboard.
>
Congratulations Kevin
--
Jaime Casanova www.2ndQuadrant.com
Professional PostgreSQL: Soporte 24x7 y capacitación
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
T
On Thu, Jun 14, 2012 at 11:41 AM, Alvaro Herrera
wrote:
> Hi,
>
> This is v12 of the foreign key locks patch.
>
Hi Álvaro,
Just noticed that this patch needs a rebase because of the refactoring
Tom did in ri_triggers.c
--
Jaime Casanova www.2ndQuadrant.com
Professiona
my patch into your prototypes?
>
so, we are waiting for a new patch? is it coming from Simon or Kohei?
--
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
oved to another place... and
don't ask, don't know why they do this...
so something reading the spclocation would have been misleading
--
Jaime Casanova www.2ndQuadrant.com
Professional PostgreSQL: Soporte 24x7 y capacitación
--
Sent via pgsql-hackers mailing list (pgsql-hackers@
On Fri, Jun 29, 2012 at 9:44 AM, Kohei KaiGai wrote:
>
> The auth_counter is just an proof-of-concept patch, so, it is helpful if you
> could provide another use case that can make sense.
>
what about pgbouncer?
--
Jaime Casanova www.2ndQuadrant.com
Professional Postgre
a problem if we put a
trigger file and the recovery.conf gets renamed to recovery.done, no?
at least that would be a problem for the standbys that still need to
be standbys
--
Jaime Casanova www.2ndQuadrant.com
Soporte y capacitación de PostgreSQL
--
Sent via pgsql-hackers mailing list
_mode should go away too
because the only existence of a standby.conf file imply we are a
standby but that is debatable)
--
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 you
bool, are you proposing to change that?
--
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
you did to reproduce this?
--
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
gle question:
> Would I be able to get the answers if I asked questions about the last
> version developed (e.g. for now, that would mean version 9.0.1)?
if you make a question in the appropiate list (which probably this
isn't, use pgsql-admin or pgsql-performance or pgsql-sql) probably
ondering what
happens in the presence of a prepared transaction (2PC), did you try
with concurrent transactions with different serialization levels?
--
Jaime Casanova www.2ndQuadrant.com
Professional PostgreSQL: Soporte y capacitación de PostgreSQL
--
Sent via pgsql-hackers
ething?)
3) the unnest() function does the same so seems intuitive what a
FOR-IN-UNNEST do
what i don't know if is this syntax could co-exist with the unnest() function?
--
Jaime Casanova www.2ndQuadrant.com
Professional PostgreSQL: Soporte y capacitación de PostgreSQL
--
Sent via p
On Wed, Nov 17, 2010 at 7:08 PM, Jaime Casanova wrote:
> On Thu, Sep 30, 2010 at 7:46 AM, Pavel Stehule
> wrote:
>> Hello
>>
>> this patch implement a new iteration construct - iteration over an
>> array. The sense of this new iteration is:
>> * a simple and
XLOG_RESTORE_POINT))
+ couldStop = true;
+
+ if (!couldStop)
+ return false;
"""
but i agree that your solution is more readible, i don't see any
problems from here
--
Jaime Casanova www.2ndQuadrant.com
Professional PostgreSQL: Soporte y capacitación de Po
ear more will change anything.
>
And people is more likely to migrate if they see some kind of hard
line, specially when migrate means a lot of work.
Actually, someone i know is targeting to migrate before the EOL, just
because the EOL exists.
--
Jaime Casanova www.2ndQuadrant.com
Professiona
(argc=2, argv=0xbfa326a8) at
bootstrap.c:417
#7 0x0827c2ea in StartChildProcess (type=StartupProcess) at postmaster.c:4488
#8 0x08280b85 in PostmasterMain (argc=3, argv=0xa4c17e8) at postmaster.c:1106
#9 0x0821730f in main (argc=3, argv=0xa4c17e8) at main.c:199
--
Jaime Casanova www.
On Wed, Apr 27, 2011 at 1:48 PM, Dave Page wrote:
> I'm pleased to announce that effective immediately, Magnus Hagander
> will be joining the PostgreSQL Core Team.
>
Congratulations!
--
Jaime Casanova www.2ndQuadrant.com
Professional PostgreSQL: Soporte y capacitación
;s used...
not even on BaseBackup() before the call to SYSTEM_IDENTIFY was removed
--
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
FULL.
>
AFAICS, the problem is that those operations involve the rebuild of
tables, so we can't simply stop in the middle and wait because we will
need to hold a strong lock more time... also the patch seems to be
only doing something for CLUSTER and not for VACUUM FULL.
or am i missin
On Sat, Apr 30, 2011 at 5:48 PM, Tom Lane wrote:
> Jaime Casanova writes:
>> On Sat, Apr 30, 2011 at 1:19 PM, Gabriele Bartolini
>>> I have noticed that during VACUUM FULL on reasonably big tables, replication
>>> lag climbs. In order to smooth down the rep
retrieved from IDENTIFY_SYSTEM so if we add it in 9.2 we will be
unable to do this until 9.3 (when both releases agree about the number
of fields returned).
patch is very simple and doesn't affect anyone nor this will require
an initdb so i guess is safe to apply now.
comments?
--
Jaime
urely. we can make it work all the
time and for any x major release? probably not.
that's why i want the XLOG_PAGE_MAGIC, but you're question about
catversion is a very good one
--
Jaime Casanova www.2ndQuadrant.com
Professional PostgreSQL: Soporte y capacitación de PostgreSQL
--
ituations: the
base type of the source and the target as we receive it and viceversa,
i think that's just complicating for a very little benefit if any...
attached (pass all regression tests), comments?
--
Jaime Casanova www.2ndQuadrant.com
Professional PostgreSQL: Soporte y capa
On Sat, May 14, 2011 at 5:13 PM, Tom Lane wrote:
> Jaime Casanova writes:
>> If i create a DOMAIN an then want to create a CAST from that domain to
>> another type it gives an error.
>
> It's *not* trivial to fix, at least not in a way that gives desirable
> behavi
should use the function syntax such as your datetime2int().
>
> That way it is easier for users to predict what behavior will occur, and
> implementation will be easier too.
>
really? how getting an error when i already have a cast on the domain
is predictable?
--
Jaime Casanova
>
Obviously it should run the cast from timestamp to int, why it will
run a cast from a domain?
the other way should be allowed, though... a cast from datetime to int
should first look for cast function using the domain and if it don't
find it then with base type
--
Jaime Casanova
should
> actually provide those tests, and not just put in an unused field.
>
actually, now is when we can play with that API at will when/if we can
make online upgrades work then we will be stuck with whatever we have
made. before that we know it won't affect anybody
--
Jaime Casanova
27;t seem obvious (to me).
>
still, we have a problem... because we are happily ignoring correctely
created casts...
at least, we should document that casts on domains are ignored and
that we should use the base types instead, maybe even a warning or a
notice when issuing the CREATE CAST c
On Sun, May 15, 2011 at 9:01 PM, Robert Haas wrote:
> On Sun, May 15, 2011 at 7:43 PM, Jaime Casanova wrote:
>> still, we have a problem... because we are happily ignoring correctely
>> created casts...
>> at least, we should document that casts on domains are ignored and
On Sun, May 15, 2011 at 6:03 PM, Jaime Casanova wrote:
> On Thu, May 5, 2011 at 10:59 AM, Tom Lane wrote:
>> Magnus Hagander writes:
>>>> So even if people don't believe in the rationale behind the patch,
>>>> would allowing it harm anything at this p
fall to
the base types...
anything else will complicate things as you shown... actually, things
looks very simple until we start creating trees of domains...
what options look sane to you?
--
Jaime Casanova www.2ndQuadrant.com
Professional PostgreSQL: Soporte y capacitación de PostgreSQL
plementation limitation i
would prefer to send a WARNING
--
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.
On Mon, May 16, 2011 at 2:35 AM, Magnus Hagander wrote:
> On Mon, May 16, 2011 at 01:03, Jaime Casanova wrote:
>> On Thu, May 5, 2011 at 10:59 AM, Tom Lane wrote:
>>> Magnus Hagander writes:
>>>>> So even if people don't believe in the rationale behind t
oked, right?
A question: why will we beign so rude by killing other sessions
instead of avoid new connections and wait until the current sessions
disconnect?
--
Jaime Casanova www.2ndQuadrant.com
Professional PostgreSQL: Soporte y capacitación de PostgreSQL
--
Sent via pgsql-hackers mail
On Fri, May 20, 2011 at 12:50 PM, Magnus Hagander wrote:
>
> Yes. It might be useful to note it, and then ust make an override
> flag. My pointm, though, was that doing it for walreceiver is more
> important and a more logical first step.
>
ok, patch attached.
--
Jaime Casan
field now... so i made a patch to use
it in pg_basebackup before the transfer starts and avoid time and
bandwith waste but Magnus prefer this in walreceiver...
--
Jaime Casanova www.2ndQuadrant.com
Professional PostgreSQL: Soporte y capacitación de PostgreSQL
diff --git a/doc/src/sgml/proto
t replicated to the standby, the clusterware can promote
> the standby safely without any data loss (to the client point of view), I
> think.
>
then, you also need to transmit to the standby if it is the current
sync standby.
--
Jaime Casanova www.2ndQuadrant.com
Professional Post
On Tue, May 31, 2011 at 11:04 AM, Alvaro Herrera
wrote:
> This patch allows you to initially declare a CHECK constraint as NOT
> VALID
seems you forgot to add the patch itself
--
Jaime Casanova www.2ndQuadrant.com
Professional PostgreSQL: Soporte y capacitación de PostgreSQL
--
arre design wouldn't matter to us even if the case did apply.
>
that's right, the debian way is pg_ctlcluster
--
Jaime Casanova www.2ndQuadrant.com
Professional PostgreSQL: Soporte y capacitación de PostgreSQL
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgr
/ 1024.0 > (double)work_disk)
- the patch adds this to serial_schedule but no test has been added...
diff --git a/src/test/regress/serial_schedule b/src/test/regress/serial_schedule
index bb654f9..325cb3d 100644
--- a/src/test/regress/serial_schedule
+++ b/src/test/regress/serial_schedule
@@ -12
objects owned
by %s because they are "
"required by the
database system",
getObjectDescription(&obj;
"""
but haven't thought of a good way of rephrase it
es we will have a *lot*
of work to do... starting by the project's name ;)
--
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://
of relations
Schema | Name | Type | Owner
+--+---+---
pg_catalog | pg_class | table | unprivileged_user
(1 row)
--
Jaime Casanova www.2ndQuadrant.com
Professional PostgreSQL: Soporte 24x7 y capacitación
--
Sent via pgsql-hackers mailing l
On Mon, Jun 6, 2011 at 6:36 AM, Peter Eisentraut wrote:
> On tis, 2011-05-17 at 14:11 -0500, Jaime Casanova wrote:
>> On Tue, May 17, 2011 at 12:19 PM, Robert Haas wrote:
>> >
>> > The more controversial question is what to do if someone tries to
>> > creat
On Mon, Jun 13, 2011 at 8:55 AM, Tom Lane wrote:
> Robert Haas writes:
>> On Mon, Jun 13, 2011 at 2:41 AM, Jaime Casanova
>> wrote:
>>> btw, i'm allowed to use ALTER TABLE to assign a new owner (even an
>>> unprivileged one) to a system catalog, probabl
On Mon, Jun 13, 2011 at 10:37 AM, Alvaro Herrera
wrote:
> Excerpts from Robert Haas's message of sáb jun 11 21:01:55 -0400 2011:
>> On Thu, Jun 9, 2011 at 1:26 PM, Jaime Casanova wrote:
>> > on shdepReassignOwned() we have this message, which is obviously wrong
>>
ge is in english which non-english dba's won't have
--
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
gt;> this is quite simple. I don't have it handy right now but I'll post it
>> soon.
>
> Here's the complete patch.
>
this doesn't apply
--
Jaime Casanova www.2ndQuadrant.com
Professional PostgreSQL: Soporte 24x7 y capacitación
--
Sent via pgsql-hack
On Tue, Jun 14, 2011 at 4:41 PM, Jaime Casanova wrote:
> On Tue, Jun 14, 2011 at 4:14 PM, Alvaro Herrera
> wrote:
>> Excerpts from Alvaro Herrera's message of lun jun 13 18:08:12 -0400 2011:
>>> Excerpts from Dean Rasheed's message of sáb jun 11 09:32:15 -0400
have tried:
EXAMPLE 1:
constraint_exclusion when using NOT VALID check constraints... and it
works well, except when the constraint has been validated, it keeps
ignoring it (which means i won't benefit from constraint_exclusion)
until i execute ANALYZE on the table or close connection
EXAM
., not replay all the available WAL records)?
>
i would prefer something like "pg_ctl promote -m immediate" that
terminates the recovery
--
Jaime Casanova www.2ndQuadrant.com
Professional PostgreSQL: Soporte 24x7 y capacitación
--
Sent via pgsql-hackers mailing list (pgsql-hac
Hi,
Testing the CHECK NOT VALID patch i found $subject... is this intended?
--
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
On Wed, Jun 15, 2011 at 3:14 PM, Alvaro Herrera
wrote:
>
> So is somebody from 2nd Quadrant going to supply a patch to fix this?
>
well, i was going to give it a try... but in a couple of hours...
--
Jaime Casanova www.2ndQuadrant.com
Professional PostgreSQL: Sopor
he code more carefully and look at the docs, but
probably this is just fine to be commited...
--
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
g, and I'll work up a patch for this tonight or at latest
> tomorrow.
>
Hi,
Are you still working on this? should we expect a new patch?
--
Jaime Casanova www.2ndQuadrant.com
Professional PostgreSQL: Soporte 24x7 y capacitación
--
Sent via pgsql-hackers mailing list (pgsql
On Fri, Jun 17, 2011 at 1:54 PM, David Fetter wrote:
> On Fri, Jun 17, 2011 at 09:57:13AM -0500, Jaime Casanova wrote:
>>
>> Are you still working on this? should we expect a new patch?
>
> Yes, sorry about that. I let work get on top of me. Will try for a
> new patch
On Thu, Jun 16, 2011 at 4:10 AM, Jaime Casanova wrote:
> On Wed, Jun 15, 2011 at 7:08 PM, Alvaro Herrera
> wrote:
>>
>> Yeah, nothing serious. Updated patch attached. The wording in the doc
>> changes could probably use some look over.
>>
>
> looks goo
select myfunc(0), current_setting('work_mem');
myfunc | current_setting
+-
! 2MB| 3MB
(1 row)
set work_mem = '3MB';
"""
it seems that the effect of SET is being discarded
--
Jaime Casanova www.2ndQuadrant.com
Profe
a lot for your help.
>
i used gmail until a couple of weeks ago and never had problems... (well
i'm still using it at least as a mail server, i just changed the
interface a access from)
--
Jaime Casanova www.2ndQuadrant.com
Professional PostgreSQL
Soporte 24x7, desarrollo, capaci
can't restore to 5 minutes before now)
mmm... a lazy idea: can't we just create a restore point wal record
*before* we actually drop the database? then we won't need to modify
logic about recovery_target_* (if it is only DROP DATABASE maybe that's
enough about complicating code)
or appropriate values.
>
also check pg_stat_replication
--
Jaime Casanova www.2ndQuadrant.com
Professional PostgreSQL
Soporte 24x7, desarrollo, capacitación y servicios
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
tored procedures..
>
well, while not in this thread i have been advocating that we should have a
column for duration... that way pg tools won't need to look for
"duration" (which makes those tools useless in non-english
installations)
--
Jaime Casanova www.2ndQuadra
KEEPINTVL and TCP_KEEPCNT we should use level SOL_TCP
but on src/interfaces/libpq/fe-connect.c we use IPPROTO_TCP instead.
any leads?
--
Jaime Casanova www.2ndQuadrant.com
Professional PostgreSQL
Soporte 24x7, desarrollo, capacitación y servicios
--
Sent via pgsql-hackers mailing
Simon Riggs writes:
> On Mon, Jul 4, 2011 at 9:42 AM, Jaime Casanova wrote:
>
>> i even used getsockopt() to ensure TCP_KEEPIDLE was being setted and
>> tried to set it myself with setsockopt() with the same results.
>
> There's a list of preconditions as to wh
On Tue, Feb 1, 2011 at 10:02 AM, Euler Taveira de Oliveira
wrote:
> Em 14-01-2011 17:41, Jaime Casanova escreveu:
>>
>> Here is a patch that implements "named restore points".
>>
> Sorry, I was swamped with work. :(
>
> Your patch no longer applied
nal review:
it works good most of the time, just a few points:
- if i interrupt the process the connections stay, i guess it could
catch the signal and finish the connections
- if i have an exclusive lock on a table and a worker starts dumping
it, it fails because it can't take the lock but it jus
201 - 300 of 850 matches
Mail list logo
