, 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
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
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
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
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
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
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
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
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
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
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
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
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
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
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)
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
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
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
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
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
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
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
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
., 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
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
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
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
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
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
>>
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 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
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
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://
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
/ 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
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
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
--
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
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
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
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 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
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.
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
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
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
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
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
>
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 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
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
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
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
--
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
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
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
;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
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
(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.
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
; 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
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
c->lwWaitLink;
}
if (proc->lwWaitLink == NULL) /* At tail */
{
! Assert(proc != MyProc);
/* Remove ourselves from tail of queue */
Assert(queue->tail == MyProc);
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
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
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
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
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
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
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
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
* Use int64 arithmetic to avoid
overflows in units
-* conversion.
-*/
--
Jaime Casanova www.2ndQuadrant.com
Professional PostgreSQL: Soporte y capacitación de PostgreSQL
On Fri, Jan 7, 2011 at 3:18 PM, Joachim Wieland wrote:
> Here's a new series of patches for the parallel dump/restore. They need to be
> applied on top of each other.
>
This one is the last version of this patch? if so, commitfest app
should be updated to reflect that
--
On Fri, Jan 14, 2011 at 8:33 PM, Euler Taveira de Oliveira
wrote:
>
> OK. I will review your patch at the beginning of the week.
>
thanks
--
Jaime Casanova www.2ndQuadrant.com
Professional PostgreSQL: Soporte y capacitación de PostgreSQL
--
Sent via pgsql-hackers mailing li
On Fri, Jan 14, 2011 at 5:42 PM, Euler Taveira de Oliveira
wrote:
> Em 14-01-2011 17:41, Jaime Casanova escreveu:
>>
>> Here is a patch that implements "named restore points".
>>
> Nice feature. I only read the provided documentation and it seems
> inconsi
imes, dates and such).
This adds a new function: pg_create_restore_point(text) (i'm not
wedded with the name so if someone wants to suggest something better,
that's fine with me), a new xlog record and a new recovery_target
parameter in recovery.conf
--
Jaime Casanova www.2ndQuadra
On Thu, Dec 2, 2010 at 10:57 PM, Tom Lane wrote:
[...]
> My answer is "no,
> and I'm not sure those things should be there in the first place".
>
i agree. after all the committers give the appropiate credit in the
commit message so if we want history it's there
-
On Mon, Nov 29, 2010 at 9:55 PM, Daniel Loureiro wrote:
> good point. But when you use a LIMIT in a SELECT statement you WANT n RANDOM
> tuples
no. at least IMHO the only sensible way that LIMIT is usefull is with
an ORDER BY clause with make the results very well defined...
--
Jaime Ca
ssible
you delete something you don't want to... the correct solution is to
use always try DELETE's inside transactions and only if you see the
right thing happening issue a COMMIT
besides i think this has been proposed and rejected before
--
Jaime Casanova www.2ndQuadrant.com
Profess
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
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
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
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
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
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
_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
201 - 300 of 850 matches
Mail list logo
