> wants to do.
>
> Agreed.
>
Doesn't makes sense implement a way to every extension register your own
cleanup code and them with DISCARD EXTENSIONS and/or DISCARD ALL run this
registered procedure?
If yes I can develop a patch to do that (actually I already start with
implementation).
Regards,
--
Fabrízio de Royes Mello
Consultoria/Coaching PostgreSQL
>> Timbira: http://www.timbira.com.br
>> Blog sobre TI: http://fabriziomello.blogspot.com
>> Perfil Linkedin: http://br.linkedin.com/in/fabriziomello
>> Twitter: http://twitter.com/fabriziomello
nd. A general hook into
> DISCARD might be doable, but then it's not clear how to categorize this
> into DISCARD subcommands.
>
I proposed some like that in a previous message [1].
Regards,
[1]
http://www.postgresql.org/message-id/cafcns+p+pmfhkiptf1xbz3neg8d0mtenb021h2fug0493
own "discard"
procedure and then the "DISCARD ALL" can execute all registered extension
cleanup procedures. Makes sense?
> Are we going to backpatch a doc change that says "releases all temporary
> resources, except for plptyhon's and plperl's GD"? Sur
messages:
- "reading indexes for table \"%s\".\"%s\"\n"
- "reading foreign key constraints for table \"%s\".\"%s\"\n"
- "reading triggers for table \"%s\".\"%s\"\n"
- "finding the columns and types of
On Thu, Apr 17, 2014 at 11:36 AM, Bruce Momjian wrote:
>
> On Thu, Apr 17, 2014 at 11:29:03AM -0300, Fabrízio de Royes Mello wrote:
> > > > This database have a lot of different schemas with same structure
and if I
> > > > need do view the status of dump I don&#x
On Thu, Apr 17, 2014 at 2:14 AM, Michael Paquier
wrote:
>
> On Thu, Apr 17, 2014 at 11:41 AM, Fabrízio de Royes Mello
> wrote:
> > Hi all,
> >
> > There are some reason to verbose output of pg_dump don't show schema
name?
> >
> > A output example
e structure and if I
need do view the status of dump I don't know what schema the table are dump
from.
Regards,
--
Fabrízio de Royes Mello
Consultoria/Coaching PostgreSQL
>> Timbira: http://www.timbira.com.br
>> Blog sobre TI: http://fabriziomello.blogspot.com
>> Perf
on't know
> > the ensuing state fully.
>
> Yeah. I think CINE is more sensible than COR for sequences, for
> precisely the reason that they do have contained data (even if it's
> basically only one value).
>
The attached patch contains CINE for sequences.
I just strip
d |val
+---
1 | 0.554413774050772
2 | 0.767866868525743
3 | 0.601187175605446
...
But fail if I change the values of between clause:
fabrizio=# select * from test where val between 0.1 and 0.19;
ERROR: tuple offset out of range: 8080
Regards,
--
F
SELECT set_config('foo.application_name', 'myapp');
4) Now you can use this functions do register the name of your application
an use it in your trigger.
Regards,
[1]
http://www.postgresql.org/docs/current/static/runtime-config-logging.html#GUC-APPLICATION-NAME
[2] http:/
omething along those lines is a good idea. I also think, maybe even
> importantly, that we should probably document that people using
> file-copy based hot backups should strongly consider removing the
> replication slots by hand before using the backup.
>
>
+1
Fabrízio
--
Fabríz
On Tue, Apr 1, 2014 at 1:40 PM, Andres Freund
wrote:
>
> On 2014-04-01 13:37:57 -0300, Fabrízio de Royes Mello wrote:
> > In the GSoC proposal page [1] I received some suggestions to strech
goals:
> >
> > * "ALTER TABLE name SET UNLOGGED". This is essentially th
that they do have contained data (even if it's
> basically only one value).
>
>
Well then I'll separate CINE for sequences for the previous rejected... is
this a material for 9.5?
Regards,
--
Fabrízio de Royes Mello
Consultoria/Coaching PostgreSQL
>> Timbira: http
not
SET UNLOGGED.
* Allow unlogged indexes on logged tables.
* Implement "ALTER TABLE name SET LOGGED" without rewriting the whole
table, when wal_level = minimal.
* Allow unlogged materialized views.
Comments?
[1]
http://www.google-melange.com/gsoc/proposal/review/student/goog
+--
> 19322 | 19313 | RI_ConstraintTrigger_a_19322 |19321
> 19323 | 19313 | RI_ConstraintTrigger_a_19323 |19321
> 19324 | 19318 | RI_ConstraintTrigger_c_19324 |19321
> 19325 | 19318 | RI_ConstraintTrigger_c_19325 |19321
> (4 rows)
&
On Tue, Apr 1, 2014 at 1:14 AM, Michael Paquier
wrote:
>
> On Tue, Apr 1, 2014 at 7:28 AM, Fabrízio de Royes Mello
> wrote:
> > Think about the statements below:
> >
> > CREATE ROLE test NOLOGIN;
> > CREATE OR REPLACE ROLE test;
> >
> > If we execute
On Mon, Mar 31, 2014 at 5:46 PM, Stephen Frost wrote:
>
> * Fabrízio de Royes Mello (fabriziome...@gmail.com) wrote:
> > Because they maintain user data?
>
> Eh? You mean like the sequence #? Yes, I'd expect 'CREATE OR REPLACE
> SEQUENCE' to want a minvalue
On Mon, Mar 31, 2014 at 5:00 PM, Stephen Frost wrote:
>
> * Fabrízio de Royes Mello (fabriziome...@gmail.com) wrote:
> > On Mon, Mar 31, 2014 at 4:52 PM, Stephen Frost
wrote:
> > >
> > > * Fabrízio de Royes Mello (fabriziome...@gmail.com) wrote:
> > &
On Mon, Mar 31, 2014 at 4:52 PM, Stephen Frost wrote:
>
> * Fabrízio de Royes Mello (fabriziome...@gmail.com) wrote:
> > - CREATE SEQUENCE [ IF NOT EXISTS ]
> > - CREATE DOMAIN [ IF NOT EXISTS ]
> > - CREATE EVENT TRIGGER [ IF NOT EXISTS ]
> > - CREATE ROLE [ IF NOT
Em segunda-feira, 31 de março de 2014, Michael Paquier <
michael.paqu...@gmail.com> escreveu:
> On Mon, Mar 31, 2014 at 1:36 PM, Fabrízio de Royes Mello
> > wrote:
> > It's a nice idea, but the deadline to students send a proposal was 21th
> > April.
> 21st
us challenges
> when it comes to generating a TupleDesc for pivot output. I thought I'd
> raise it in case anyone has looked into this and has any comments on
> whether this'd be a viable GSoC for an interested student.
>
It's a nice idea, but the deadline to students send
gt; But I think this patch just makes things even more surprising when
> default_with_oids is turned on.
>
Something like the attached ?
Grettings,
--
Fabrízio de Royes Mello
Consultoria/Coaching PostgreSQL
>> Timbira: http://www.timbira.com.br
>> Blog sobre TI: http:/
On Sun, Mar 2, 2014 at 1:04 AM, Fabrízio de Royes Mello <
fabriziome...@gmail.com> wrote:
>
> On Sat, Mar 1, 2014 at 7:39 PM, Tom Lane wrote:
> >
> > =?ISO-8859-1?Q?Fabr=EDzio_de_Royes_Mello?=
writes:
> > > On Sat, Mar 1, 2014 at 2:11 PM, Tom Lane wrote:
>
ion (syntax) of SECLABELs and
COMMENTs are similar. They describe something about objects, they have
local and shared catalog.
This is just something that occurred to me. Maybe I'm completely wrong. Or
not!
Comments?
--
Fabrízio de Royes Mello
Consultoria/Coaching PostgreSQL
>> Timbir
item:
* Allow an unlogged table to be changed to logged
We already discussed a while about this feature [1].
Regards,
[1]
http://www.postgresql.org/message-id/CAFcNs+peg3VPG2=v6lu3vfcdp8mt7cs6-rmmxxjxwnlregs...@mail.gmail.com
--
Fabrízio de Royes Mello
Consultoria/Coaching PostgreSQL
>> Tim
On Thu, Mar 13, 2014 at 10:22 AM, Robert Haas wrote:
>
> On Wed, Mar 12, 2014 at 11:11 PM, Fabrízio de Royes Mello
> wrote:
> > Hi all,
> >
> > Shouldn't the "ALTER" statements below raise an exception?
> >
> > fabrizio=# CREA
On Thu, Mar 13, 2014 at 10:34 AM, Euler Taveira
wrote:
>
> On 13-03-2014 00:11, Fabrízio de Royes Mello wrote:
> > Shouldn't the "ALTER" statements below raise an exception?
> >
> For consistency, yes. Who cares? I mean, there is no harm in resetting
> an un
oname" obviously will raise an
exception:
fabrizio=# ALTER TABLE foo SET (noname=1);
ERROR: unrecognized parameter "noname"
fabrizio=# ALTER INDEX foo_pkey SET (noname=1);
ERROR: unrecognized parameter "noname"
fabrizio=# ALTER TABLE foo ALTER COLUMN bar SET (noname=1);
ERROR:
ct
> and/or not accessed. Searching for badly set options needs to be
> possible, even easy, but hard validation can cause problems. And if we
> try and force it, whats to stop people from using a dummy validator
> just to circumvent the strictness?
>
Then I think my patch is more adh
e set of options and values then we are hosed.
>
> -1 to *requiring* validation for table-level options for exactly the
> same reasons we no longer validate custom GUCs.
>
In a previous email [1] I asked about alternatives to drive the work but
unfortunately no one replied. So becau
On Fri, Mar 7, 2014 at 5:56 PM, Alvaro Herrera wrote:
> I am reworking this patch, both to accomodate earlier review comments
> and to fix the multiple verify step of namespaces, as noted by Tom in
> 4530.1390023...@sss.pgh.pa.us
>
>
Alvaro,
Do you need some help?
Regards,
On Fri, Mar 7, 2014 at 7:21 PM, Andres Freund wrote:
> On 2014-03-07 19:14:48 -0300, Fabrízio de Royes Mello wrote:
> > On Fri, Mar 7, 2014 at 5:56 PM, Alvaro Herrera >wrote:
> >
> > > I am reworking this patch, both to accomodate earlier review comments
> > >
On Fri, Mar 7, 2014 at 5:56 PM, Alvaro Herrera wrote:
> I am reworking this patch, both to accomodate earlier review comments
> and to fix the multiple verify step of namespaces, as noted by Tom in
> 4530.1390023...@sss.pgh.pa.us
>
>
This link is broken...
--
Fabrízio de Royes Me
that 'vacuum full' does, but changing relpersistence
to RELPERSISTENCE_UNLOGGED for the new relfilenode. Is this?
Regards,
--
Fabrízio de Royes Mello
Consultoria/Coaching PostgreSQL
>> Timbira: http://www.timbira.com.br
>> Blog sobre TI: http://fabriziomello.blogspot.com
>> Per
On Thu, Mar 6, 2014 at 5:04 PM, Robert Haas wrote:
>
> On Thu, Mar 6, 2014 at 2:52 PM, Fabrízio de Royes Mello
> wrote:
> > On Thu, Mar 6, 2014 at 4:42 PM, Robert Haas
wrote:
> >> I think this isn't a good design. Per the discussion between Andres
> >> and
On Thu, Mar 6, 2014 at 5:05 PM, Fabrízio de Royes Mello <
fabriziome...@gmail.com> wrote:
>
>
> On Thu, Mar 6, 2014 at 5:04 PM, Robert Haas wrote:
> >
> > On Thu, Mar 6, 2014 at 2:52 PM, Fabrízio de Royes Mello
> > wrote:
> > > On Thu, Mar 6, 2014 at 4
On Thu, Mar 6, 2014 at 5:04 PM, Robert Haas wrote:
>
> On Thu, Mar 6, 2014 at 2:52 PM, Fabrízio de Royes Mello
> wrote:
> > On Thu, Mar 6, 2014 at 4:42 PM, Robert Haas
wrote:
> >> I think this isn't a good design. Per the discussion between Andres
> >> and
ll set
> a different relpersistence for the new relfilenode. If you do it that
> way, this will be less efficient, but much simpler, and you might
> actually finish it in one summer.
>
Do it like 'VACUUM FULL' for any wal_level?
Regards,
--
Fabrízio de Royes Mello
Consul
Hi all,
There are some place with the next commitfest deadlines (2014/06 and
2014/09) ?
Regards,
--
Fabrízio de Royes Mello
Consultoria/Coaching PostgreSQL
>> Timbira: http://www.timbira.com.br
>> Blog sobre TI: http://fabriziomello.blogspot.com
>> Perfil Linkedin: http://
On Tue, Mar 4, 2014 at 5:00 PM, Fabrízio de Royes Mello <
fabriziome...@gmail.com> wrote:
>
>
> On Tue, Mar 4, 2014 at 3:29 PM, Andres Freund
wrote:
> >
> > On 2014-03-04 12:54:02 -0500, Robert Haas wrote:
> > > On Tue, Mar 4, 2014 at 9:50 AM, Andres Freund
w
On Wed, Mar 5, 2014 at 5:32 PM, Rohit Goyal wrote:
>
> Hi All,
>
> Is there any ways by which i can disable the hot-update functionality?
>
Why do you want do that?
Grettings,
--
Fabrízio de Royes Mello
Consultoria/Coaching PostgreSQL
>> Timbira: http://www.timbira.co
On Wed, Mar 5, 2014 at 4:06 PM, Robert Haas wrote:
>
> On Tue, Mar 4, 2014 at 3:33 PM, Fabrízio de Royes Mello
> wrote:
> > Is the TODO item "CREATE SCHEMA ... LIKE ..." [1] a good GSoC project?
>
> Maybe. I'm not sure that everyone would agree that it's
Hi all,
Is the TODO item "CREATE SCHEMA ... LIKE ..." [1] a good GSoC project?
Regards
[1] http://wiki.postgresql.org/wiki/Todo
--
Fabrízio de Royes Mello
Consultoria/Coaching PostgreSQL
>> Timbira: http://www.timbira.com.br
>> Blog sobre TI: http://fabriziomello.
his internals, but I am willing to learn and I
think the GSoC is a good opportunity.
Any of you are willing to mentoring this project?
Regards,
--
Fabrízio de Royes Mello
Consultoria/Coaching PostgreSQL
>> Timbira: http://www.timbira.com.br
>> Blog sobre TI: http://fabriziomello.blogspot.com
>> Perfil Linkedin: http://br.linkedin.com/in/fabriziomello
>> Twitter: http://twitter.com/fabriziomello
On Tue, Mar 4, 2014 at 11:50 AM, Andres Freund
wrote:
>
> On 2014-03-04 09:47:08 -0500, Robert Haas wrote:
> > On Mon, Mar 3, 2014 at 12:08 PM, Stephen Frost
wrote:
> > > * Robert Haas (robertmh...@gmail.com) wrote:
> > >> On Mon, Mar 3, 2014 at 11:28 AM, Fabr
On Tue, Mar 4, 2014 at 3:31 AM, Andres Freund
wrote:
>
> On 2014-03-04 01:10:50 -0300, Fabrízio de Royes Mello wrote:
> > Today I do something like that:
> >
> > 1) create unlogged table tmp_foo ...
> > 2) populate 'tmp_foo' table (ETL scripts or whatev
;
ERROR: value too long for type character varying(2)
DETAIL: insert into foo values ('XXX');
or
fabrizio=# \set ECHO error
fabrizio=# insert into foo values ('XXX');
ERROR: value too long for type character varying(2)
QUERY: insert into foo values ('XXX');
Thi
On Mon, Mar 3, 2014 at 2:42 PM, Andres Freund
wrote:
>
> On 2014-03-03 12:08:26 -0500, Stephen Frost wrote:
> > * Robert Haas (robertmh...@gmail.com) wrote:
> > > On Mon, Mar 3, 2014 at 11:28 AM, Fabrízio de Royes Mello
> > > wrote:
> > > > Is the TODO
On Mon, Mar 3, 2014 at 5:47 PM, Andres Freund
wrote:
>
> On 2014-03-03 12:44:26 -0800, Peter Geoghegan wrote:
> > On Mon, Mar 3, 2014 at 8:28 AM, Fabrízio de Royes Mello
> > wrote:
> > > Is the TODO item "make an unlogged table logged" [1] a good GSoC
project
On Mon, Mar 3, 2014 at 5:44 PM, Peter Geoghegan wrote:
>
> On Mon, Mar 3, 2014 at 8:28 AM, Fabrízio de Royes Mello
> wrote:
> > Is the TODO item "make an unlogged table logged" [1] a good GSoC
project?
>
> Another interesting project around unlogged tables would b
pdate pg_class set relpersistence = 'p' where oid = 'tmp_foo':regclass
6) drop table foo; -- the old foo table
7) alter table tmp_foo rename to foo;
8) end transaction
9) run pg_repack in table 'foo'
I know it's very ugly, but works... and works for sta
Hi all,
Is the TODO item "make an unlogged table logged" [1] a good GSoC project?
Regards,
[1]
http://www.postgresql.org/message-id/aanlktinenzbrxdcwohkqbba2bhubfy8_c5jwrxlod...@mail.gmail.com
--
Fabrízio de Royes Mello
Consultoria/Coaching PostgreSQL
>> Timbira: http://ww
for client programs. This
> is helpful for QE/QA teams evaluating Postgres, and it could be
> extended for other things like replication test suite as well as far
> as I understood.
>
+1
--
Fabrízio de Royes Mello
Consultoria/Coaching PostgreSQL
>> Timbira: http://www.tim
valently fakable if the system doesn't supply the functionality.
>
You are completely right.
But we already have "DROP ... IF EXISTS", then I think if we would have
"CREATE ... IF NOT EXISTS" (the inverse behavior) will be very natural...
and I agree in imp
$ psql --help-command=vacuum
Command: VACUUM
Description: garbage-collect and optionally analyze a database
Syntax:
VACUUM [ ( { FULL | FREEZE | VERBOSE | ANALYZE } [, ...] ) ] [ table_name [
(column_name [, ...] ) ] ]
VACUUM [ FULL ] [ FREEZE ] [ VERBOSE ] [ table_name ]
VACUUM [ FULL ] [ FREEZE ]
with many servers
and many automated tasks in different pipelines, CINE will be very useful.
I have this kind of troubles mostly with functions (we use COR), and
sometimes we will discover that the production version of function is wrong
after we receive a user notify, and in this situation many tim
n the next commit fest I have time and do a
rework on it.
Regards,
--
Fabrízio de Royes Mello
Consultoria/Coaching PostgreSQL
>> Timbira: http://www.timbira.com.br
>> Blog sobre TI: http://fabriziomello.blogspot.com
>> Perfil Linkedin: http://br.linkedin.com/in/fabriziomello
>> Twitter: http://twitter.com/fabriziomello
l CREATE objects this task will more
easy because we just run it again without care if will replace the content
and do not produce an error.
I know that is a very specific case, but in my mind I don't see any problem
to have CINE and COR to this objects. The behavior is totally different.
Re
On Fri, Feb 28, 2014 at 3:44 PM, Alvaro Herrera
wrote:
>
> Fabrízio de Royes Mello escribió:
> > On Fri, Feb 28, 2014 at 3:17 PM, Pavel Stehule
> > wrote:
>
> > > important is a placing in --help output
> >
> > Well, then we just have to add more inf
t this simplifies what
>> beginners need to learn.
>
>
> three chars is not important
>
> important is a placing in --help output
>
Well, then we just have to add more info to --help
Regards,
--
Fabrízio de Royes Mello
Consultoria/Coaching PostgreSQL
>> Timbira: h
e, the tests pass, and the code looks
> OK to me. I don't have a strong opinion on validating custom reloption
> values through hooks as discussed earlier in the thread, but the simple
> version (i.e. your latest patch) seems at least a useful starting point.
>
Thanks for your review.
mention their names
> when they try to contribute.
>
Hey guys, I'm not worried about it... to me the most important thing is the
improvement and the learning. So I'm happy to help in some way.
Regards,
--
Fabrízio de Royes Mello
Consultoria/Coaching PostgreSQL
>> Timbira: h
h-so-many-years). Perhaps
> another candidate to be a GSoC project.
>
I would like to participate the GSoC this year as a student.
Regards,
--
Fabrízio de Royes Mello
Consultoria/Coaching PostgreSQL
>> Timbira: http://www.timbira.com.br
>> Blog sobre TI: http://fabriziomello.blogsp
On Sun, Feb 9, 2014 at 2:22 PM, Fabrízio de Royes Mello <
fabriziome...@gmail.com> wrote:
>
>
> On Sat, Jan 11, 2014 at 2:47 AM, Peter Eisentraut wrote:
> >
> > On Sat, 2014-01-11 at 00:48 -0200, Fabrízio de Royes Mello wrote:
> > > > Now, if bdr is inst
On Thu, Feb 13, 2014 at 12:04 AM, Bruce Momjian wrote:
>
> On Thu, Nov 21, 2013 at 11:59:51PM -0200, Fabrízio de Royes Mello wrote:
> > On Fri, Oct 25, 2013 at 3:37 PM, fabriziomello
wrote:
> > >
> > > On 2013-09-18 15:15:55 +0200, Bernd Helmle wrote:
> > >
On Sat, Jan 11, 2014 at 2:47 AM, Peter Eisentraut wrote:
>
> On Sat, 2014-01-11 at 00:48 -0200, Fabrízio de Royes Mello wrote:
> > > Now, if bdr is installed but the validation doesn't happen unless
> > bdr
> > > is "loaded" in some sense, then that
; Diff); 'normal' or 'plain' diff formats are not acceptable.
>
Would be nice if we can use "git apply" command...
:-)
--
Fabrízio de Royes Mello
Consultoria/Coaching PostgreSQL
>> Timbira: http://www.timbira.com.br
>> Blog sobre TI: http://fabri
sed to create an extension.
Regards,
[1] https://github.com/jconway/pg_controldata
--
Fabrízio de Royes Mello
Consultoria/Coaching PostgreSQL
>> Timbira: http://www.timbira.com.br
>> Blog sobre TI: http://fabriziomello.blogspot.com
>> Perfil Linkedin: http://br.linkedin.com/in/fabriziomello
>> Twitter: http://twitter.com/fabriziomello
e, then that is an implementation deficiency
> that I think we can insist be rectified before this feature is accepted.
>
Check if extension is already installed is not enough for the first version
of this feature?
Regards,
--
Fabrízio de Royes Mello
Consultoria/Coaching PostgreSQL
>> Ti
On Wed, Jan 8, 2014 at 8:43 PM, Joshua D. Drake
wrote:
>
>
> On 01/08/2014 02:38 PM, Josh Berkus wrote:
>>
>>
>> On 01/08/2014 02:04 PM, Peter Eisentraut wrote:
>>>
>>> Anyone else?
>>>
>>> Or you'll have to deal with me agai
sion is loaded then in partial
restore it can be fail. At this point we have two choices:
1) do not check if extension already is loaded
2) hack the pg_dump to produce an "ALTER TABLE ... SET (...)" instead of
"CREATE TABLE ... WITH (...)" to set reloptions
Com
nearly no "namespaced" GUCs exist (plperl,
> plpgsql have some), but postgres defines at least autovacuum. and
> toast. namespaces for relation options.
>
autovacuum. namespace ???
The HEAP_RELOPT_NAMESPACES (src/include/access/reloptions.h) constant
define only "toast
On Tue, Dec 31, 2013 at 10:37 AM, Pavel Stehule
wrote:
>
> 2013/12/31 Fabrízio de Royes Mello
>>
>> On Tue, Dec 31, 2013 at 9:38 AM, Pavel Stehule
wrote:
>> >
>> > 2013/12/31 Fabrízio de Royes Mello
>> >>
>> >> On Tue, Dec 31, 201
On Tue, Dec 31, 2013 at 9:38 AM, Pavel Stehule
wrote:
>
>
> 2013/12/31 Fabrízio de Royes Mello
>>
>>
>> On Tue, Dec 31, 2013 at 9:08 AM, Pavel Stehule
wrote:
>> >
>> > Hello
>> >
>> > I am looking on this patch
>> >
>>
egards,
[1]
http://www.postgresql.org/message-id/CAFcNs+rqCq1H5eXW-cvdti6T-xo2STEkhjREx=odmakk5ti...@mail.gmail.com
--
Fabrízio de Royes Mello
Consultoria/Coaching PostgreSQL
>> Timbira: http://www.timbira.com.br
>> Blog sobre TI: http://fabriziomello.blogspot.com
>> Perfil Linkedin: http://br.linkedin.com/in/fabriziomello
>> Twitter: http://twitter.com/fabriziomello
omplain if we broke the API by starting to throw an exception
> > on PQexec with a string containing no actual query.
>
> (Untested). Isn't this just a case of psql not printing out a timing if
> the server responds with PGRES_EMPTY_QUERY?
>
Works... look to the attached patc
eter or not. It could just assume
> that you meant the active timezone.
>
+1. And if you want a different timezone you can just set the 'timezone'
GUC.
Regards,
--
Fabrízio de Royes Mello
Consultoria/Coaching PostgreSQL
>> Timbira: http://www.timbira.com.br
>> Blog sobr
On Fri, Dec 13, 2013 at 3:53 PM, Martijn van Oosterhout
wrote:
>
> On Thu, Dec 12, 2013 at 08:50:26PM -0200, Fabrízio de Royes Mello wrote:
> > On Thu, Dec 12, 2013 at 3:11 PM, Pavel Stehule wrote:
> >
> > > Hello
> > >
> > > this patch try
rote:
> >> >> On 12 December 2013 21:58, Fabrízio de Royes Mello
> >> >> wrote:
> >> >> > Reviewing the committed patch I noted that the
"CheckForStandbyTrigger()"
> >> >> > after the delay was removed.
> >> >&
to 'UTC';
SET
fabrizio=# select '2013-12-13 11:29:45.786937'::timestamptz;
timestamptz
---
2013-12-13 11:29:45.786937+00
(1 row)
Regards,
--
Fabrízio de Royes Mello
Consultoria/Coaching PostgreSQL
>> Timbira: http://www.timbira.c
On Thu, Dec 12, 2013 at 3:11 PM, Pavel Stehule wrote:
> Hello
>
> this patch try to complete a set of functions make_date and make_timestamp.
>
>
Could we have the 'make_timestamptz' function too?
Regards,
--
Fabrízio de Royes Mello
Consultoria/Coaching Po
On Thu, Dec 12, 2013 at 3:42 PM, Fabrízio de Royes Mello <
fabriziome...@gmail.com> wrote:
>
> On Thu, Dec 12, 2013 at 3:39 PM, Simon Riggs
wrote:
> >
> > On 12 December 2013 15:19, Simon Riggs wrote:
> >
> > > Don't panic guys! I meant UTC offset onl
On Thu, Dec 12, 2013 at 3:39 PM, Simon Riggs wrote:
>
> On 12 December 2013 15:19, Simon Riggs wrote:
>
> > Don't panic guys! I meant UTC offset only. And yes, it may not be
> > needed, will check.
>
> Checked, all non-UTC TZ offsets work without further effort
; pause_at_recovery_target.
>
> In which scenarios does your restriction actually improve anything?
>
Given your arguments I'm forced to review my understanding of the problem.
You are absolutely right in your assertions. I was not seeing the scenario
on this perspective.
Anyw
delay the Streaming Replication, so if the
slave server isn't a hot-standby I think makes no sense to delay it.
Mitsumasa suggested to add "StandbyModeRequested" in conditional branch to
skip this situation. I agree with him!
And I'll change 'recoveryDelay' (function
On Sat, Dec 7, 2013 at 11:41 PM, Fabrízio de Royes Mello <
fabriziome...@gmail.com> wrote:
>
>
> On Sat, Dec 7, 2013 at 11:20 PM, Michael Paquier <
michael.paqu...@gmail.com> wrote:
> > >
> > > IMHO is more elegant create a procedure to encapsulate the
is first moment we can just create a procedure inside the
dblink contrib and not touch in libpq.
Regards,
--
Fabrízio de Royes Mello
Consultoria/Coaching PostgreSQL
>> Timbira: http://www.timbira.com.br
>> Blog sobre TI: http://fabriziomello.blogspot.com
>> Perfil Linkedin: http:
s! Will make that change.
>
> Committed to all active branches.
>
IMHO is more elegant create a procedure to encapsulate the code to avoid
redundancy.
Regards,
--
Fabrízio de Royes Mello
Consultoria/Coaching PostgreSQL
>> Timbira: http://www.timbira.com.br
>> Blog sobre TI: http://fabriziomello.blogspot.com
>> Perfil Linkedin: http://br.linkedin.com/in/fabriziomello
>> Twitter: http://twitter.com/fabriziomello
On Fri, Dec 6, 2013 at 1:36 PM, Robert Haas wrote:
> On Thu, Dec 5, 2013 at 11:07 PM, Fabrízio de Royes Mello
> wrote:
> > On Tue, Dec 3, 2013 at 5:33 PM, Simon Riggs
> wrote:
> >>
> >> > - compute recoveryUntilDelayTime in XLOG_XACT_COMMIT and
&g
On Fri, Dec 6, 2013 at 2:50 AM, Joe Conway wrote:
>
> On 12/05/2013 07:16 PM, Fabrízio de Royes Mello wrote:
> > Hi Joe, how are you?
>
> Hi Fabrizio -- great to hear from you! I'm well.
>
:-)
> > Well, when Tom sent this email I was reviewing your patch and
s to apply all
> data received as quickly as possible once triggered, so the specified
> delay does not slow down promoting the server to a master. That might
> also be seen as a negative behaviour, since promoting the master
> effectively sets recovery_time_delay to zero.
>
> I will
ing your patch and the main
suggestion is about use of 'pg_encoding_to_char' too... ;-)
The attached patch with my review!
Regards,
--
Fabrízio de Royes Mello
Consultoria/Coaching PostgreSQL
>> Timbira: http://www.timbira.com.br
>> Blog sobre TI: http://fabriziomello.blo
t; critically reliant on time synchronisation, we are OK to proceed with
> this specific feature.
>
>
Hi all,
I saw the comments of all of you. I'm a few busy with some customers issues
(has been a crazy week), but I'll reply and/or fix your suggestions later.
t; delayed standby was replicated after exactly 5 minutes. I did not
> notice any problems, errors or warnings.
>
>
Thanks for your review Christian...
Regards,
--
Fabrízio de Royes Mello
Consultoria/Coaching PostgreSQL
>> Timbira: http://www.timbira.com.br
>> Blog sobre TI
connect to it using psql and in another session I
can see all archive recovery log
> My first easy review of your patch is that all.
>
Thanks.
Regards,
--
Fabrízio de Royes Mello
Consultoria/Coaching PostgreSQL
>> Timbira: http://www.timbira.com.br
>> Blog sobre TI: http://f
-peg-the-xmin-horizon-for-catalog-t.patch.gz
| git apply -
warning: src/backend/access/transam/xlog.c has type 100755, expected 100644
$ gunzip -c
/home/fabrizio/Downloads/0011-wal_decoding-pg_recvlogical-Introduce-pg_receivexlog.patch.gz
| git apply -
error: patch failed: src/bin/pg_basebackup/strea
On Thu, Nov 21, 2013 at 11:06 AM, Robert Haas wrote:
>
> On Wed, Nov 20, 2013 at 9:35 PM, Fabrízio de Royes Mello
> wrote:
> >> > So, with this patch we can do that:
> >> >
> >> > ALTER TABLE foo
> >> >SET (ext.somext.do_replicate=tru
isabled the constraint but the trigger. Especially as we
> > already have NOT VALID and might grow DISABLED for constraint
> > themselves...
> >
>
> Hi,
>
> The attached patch [1] enable PSQL to list internal disabled triggers in
\d
> only in versions >= 9.0.
>
&g
On Thu, Nov 21, 2013 at 12:05 AM, Robert Haas wrote:
>
> On Wed, Nov 20, 2013 at 1:52 PM, Fabrízio de Royes Mello
> wrote:
> > The main goal of this patch is enable to an user the capability to store
> > options
> > (relations and attributes) related to extensi
ALTER TABLE foo
SET (ext.somext.do_replicate=true);
When 'ext' is the fixed prefix, 'somext' is the extension name,
'do_replicate' is the
extension option and 'true' is the value.
Also we can use this form to define storage options to indexes and
per-at
301 - 400 of 467 matches
Mail list logo
