set pgsql-hackers digest
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
, because
the OS already has the capability to schedule and maintain the tasks.
Best regards,
--
Fabrízio de Royes Mello
Consultoria/Coaching PostgreSQL
Blog sobre TI: http://fabriziomello.blogspot.com
Perfil Linkedin: http://br.linkedin.com/in/fabriziomello
Twitter: http://twitter.com/fabriziomello
can write a patch to put Valid until into attributes
column.
--
Fabrízio de Royes Mello
Consultoria/Coaching PostgreSQL
Blog sobre TI: http://fabriziomello.blogspot.com
Perfil Linkedin: http://br.linkedin.com/in/fabriziomello
Twitter: http://twitter.com/fabriziomello
, Create role, Create DB, Replication
| {}|
Regards,
--
Fabrízio de Royes Mello
Consultoria/Coaching PostgreSQL
Blog sobre TI: http://fabriziomello.blogspot.com
Perfil Linkedin: http://br.linkedin.com/in/fabriziomello
Twitter: http://twitter.com/fabriziomello
the OP's complaint, it's particularly
important for those who have forgotten they're using the feature
(and hence would not think to specify + ...)
You' re right, then I attached a new patch with your suggestion.
Regards,
--
Fabrízio de Royes Mello
Consultoria/Coaching PostgreSQL
Blog sobre TI
| 2012-12-26 12:11:54-02
fabrizio | 2012-12-26 12:12:02-02
(4 rows)
This isn't an elegant solution to do that, but worked fine. However, why
not we have a column to store this information?
Somebody have another idea?
Regards,
--
Fabrízio de Royes Mello
Consultoria/Coaching PostgreSQL
Blog sobre
a single column datcreated
on shared catalog pg_database.
[1] http://www.postgresql.org/docs/devel/static/event-trigger-matrix.html
Regards,
--
Fabrízio de Royes Mello
Consultoria/Coaching PostgreSQL
Blog sobre TI: http://fabriziomello.blogspot.com
Perfil Linkedin: http://br.linkedin.com
?
+1
If all of you agree I can improve the event trigger docs...
Regards,
--
Fabrízio de Royes Mello
Consultoria/Coaching PostgreSQL
Blog sobre TI: http://fabriziomello.blogspot.com
Perfil Linkedin: http://br.linkedin.com/in/fabriziomello
Twitter: http://twitter.com/fabriziomello
Hi all,
And about proposal that originated this thread... I proposed only to add a
column on shared catalog pg_database with timestamp of its creation.
Event triggers don't cover CREATE DATABASE statement.
Regards,
--
Fabrízio de Royes Mello
Consultoria/Coaching PostgreSQL
Blog sobre TI
Hi all,
When we execute 'make clean' the file 'src/backend/replication/repl_gram.h'
is not removed.
The attached patch fix it.
Regards,
--
Fabrízio de Royes Mello
Consultoria/Coaching PostgreSQL
Blog sobre TI: http://fabriziomello.blogspot.com
Perfil Linkedin: http://br.linkedin.com
... thanks
--
Fabrízio de Royes Mello
Consultoria/Coaching PostgreSQL
Blog sobre TI: http://fabriziomello.blogspot.com
Perfil Linkedin: http://br.linkedin.com/in/fabriziomello
Twitter: http://twitter.com/fabriziomello
the timestamp of database creation.
If this feature is approved I could extend it to add a column into
'pg_class' to store creation timestamp too.
I think we can discuss about psql support to show this new info about
databases...
Regards,
--
Fabrízio de Royes Mello
Consultoria/Coaching
On Thu, Jan 3, 2013 at 11:13 AM, Stephen Frost sfr...@snowman.net wrote:
* Fabrízio de Royes Mello (fabriziome...@gmail.com) wrote:
The attached patch add a new column into 'pg_database' called
'datcreated'
to store the timestamp of database creation.
Please use hard-tabs (not spaces
On Thu, Jan 3, 2013 at 11:33 AM, Fabrízio de Royes Mello
fabriziome...@gmail.com wrote:
On Thu, Jan 3, 2013 at 11:13 AM, Stephen Frost sfr...@snowman.net wrote:
* Fabrízio de Royes Mello (fabriziome...@gmail.com) wrote:
The attached patch add a new column into 'pg_database' called
On Thu, Jan 3, 2013 at 11:41 AM, Stephen Frost sfr...@snowman.net wrote:
* Fabrízio de Royes Mello (fabriziome...@gmail.com) wrote:
On Thu, Jan 3, 2013 at 11:13 AM, Stephen Frost sfr...@snowman.net
wrote:
Please use hard-tabs (not spaces) and the column should come before the
variable
going to this way I think yes...
As Peter said we can start add it for a few commands in one release (maybe
first for shared objects) and then for a few more commands in a next
release, and next... until we cover all commands...
Regards,
--
Fabrízio de Royes Mello
Consultoria/Coaching PostgreSQL
decide what to do.
I don't know enough, but I have another idea. What you guys think about we
have tables like stats tables to track creation times, with a GUC to
enable or disable this behavior.
Regards,
[1] http://archives.postgresql.org/pgsql-hackers/2013-01/msg00111.php
--
Fabrízio de
* Stephen Frost sfr...@snowman.net wrote:
* Fabrízio de Royes Mello (fabriziome...@gmail.com) wrote:
* also we discuss about create two new catalogs, one local and another
shared (like pg_description and pg_shdescription) to track creation
times
of all database objects.
Creating
thoughts on this and perhaps we should create a wiki page
to start documentating the semantics. Once we get agreement there, it's
just a bit of code. :)
+1
Regards,
--
Fabrízio de Royes Mello
Consultoria/Coaching PostgreSQL
Blog sobre TI: http://fabriziomello.blogspot.com
Perfil Linkedin: http
.
The attached patch is ok for me and ready for commit.
Regards,
--
Fabrízio de Royes Mello
Consultoria/Coaching PostgreSQL
Blog sobre TI: http://fabriziomello.blogspot.com
Perfil Linkedin: http://br.linkedin.com/in/fabriziomello
Twitter: http://twitter.com/fabriziomello
rows directly in the pg_triggers table …. I
need to fix it.
Maybe you simply DROP and CREATE trigger solve it...
Regards,
--
Fabrízio de Royes Mello
Consultoria/Coaching PostgreSQL
Blog sobre TI: http://fabriziomello.blogspot.com
Perfil Linkedin: http://br.linkedin.com/in/fabriziomello
Twitter
a DO statement every time I needed it (which
in migration scripts is fairly often).
I understand your difficulty.
Regards,
--
Fabrízio de Royes Mello
Consultoria/Coaching PostgreSQL
Blog sobre TI: http://fabriziomello.blogspot.com
Perfil Linkedin: http://br.linkedin.com/in/fabriziomello
2012/8/15 David E. Wheeler da...@justatheory.com
On Aug 15, 2012, at 11:31 AM, Fabrízio de Royes Mello wrote:
Is there any reason not to add $subject? Would it be difficult?
Looking to the source code I think this feature isn't hard to
implement... I'm writing a little path to do
2012/8/16 David E. Wheeler da...@justatheory.com
On Aug 16, 2012, at 10:36 AM, Fabrízio de Royes Mello wrote:
The attached patch implement this feature:
CREATE SCHEMA [ IF NOT EXISTS ] schema_name [ AUTHORIZATION user_name ]
[ schema_element [ ... ] ]
CREATE SCHEMA [ IF NOT EXISTS
2012/8/16 Dickson S. Guedes lis...@guedesoft.net
2012/8/16 Fabrízio de Royes Mello fabriziome...@gmail.com:
The attached patch implement this feature:
CREATE SCHEMA [ IF NOT EXISTS ] schema_name [ AUTHORIZATION user_name ] [
schema_element [ ... ] ]
CREATE SCHEMA [ IF NOT EXISTS
2012/8/17 Fabrízio de Royes Mello fabriziome...@gmail.com
I started testing this, but I didn't see regression tests for it.
Could you write them?.
The attached patch contains regression tests for it.
Please, don't consider de last patch (v2) because I make a little mistake
completely right, thanks...
The attached patch add support for the new field in the node in
copyfuncs.c and equalfuncs.c.
Regards,
--
Fabrízio de Royes Mello
Consultoria/Coaching PostgreSQL
Blog sobre TI: http://fabriziomello.blogspot.com
Perfil Linkedin: http://br.linkedin.com
2012/8/17 Alvaro Herrera alvhe...@2ndquadrant.com
Excerpts from Dickson S. Guedes's message of vie ago 17 10:37:25 -0400
2012:
2012/8/17 Fabrízio de Royes Mello fabriziome...@gmail.com:
2012/8/17 Alvaro Herrera alvhe...@2ndquadrant.com
Excerpts from Fabrízio de Royes Mello's
,
--
Fabrízio de Royes Mello
Consultoria/Coaching PostgreSQL
Blog sobre TI: http://fabriziomello.blogspot.com
Perfil Linkedin: http://br.linkedin.com/in/fabriziomello
Twitter: http://twitter.com/fabriziomello
://www.postgresql.org/docs/9.2/interactive/sql-createschema.html
--
Fabrízio de Royes Mello
Consultoria/Coaching PostgreSQL
Blog sobre TI: http://fabriziomello.blogspot.com
Perfil Linkedin: http://br.linkedin.com/in/fabriziomello
Twitter: http://twitter.com/fabriziomello
and implement, and I think it covers all the sane use-cases
anyway.
I thought we'd already agreed on this.
Well, it's not what the latest proposed patch implements.
You're right... the latest proposed patch don't implements it.
I'll change the patch and send soon...
Regards,
--
Fabrízio de
2012/10/2 Fabrízio de Royes Mello fabriziome...@gmail.com
You're right... the latest proposed patch don't implements it.
I'll change the patch and send soon...
What is more reasonable?
* show a syntax error or
* show a message that you can not use the INE with contained objects
Regards
2012/10/3 Alvaro Herrera alvhe...@2ndquadrant.com
Excerpts from Fabrízio de Royes Mello's message of mié oct 03 09:27:41
-0300 2012:
2012/10/2 Fabrízio de Royes Mello fabriziome...@gmail.com
You're right... the latest proposed patch don't implements it.
I'll change the patch
=# CREATE SCHEMA IF NOT EXISTS test_schema_1
CREATE TABLE abc (
a serial,
b int UNIQUE
);
ERROR: IF NOT EXISTS cannot be used with schema elements
LINE 1: CREATE SCHEMA IF NOT EXISTS test_schema_1
^
Time: 0,773 ms
Regards,
--
Fabrízio de
row)
Should I continue working on this patch?
Hi all,
If it can help, Euler wrote about that some time ago in your blog [1].
Regards,
[1] http://eulerto.blogspot.com.br/2010/11/comment-on-catalog-tables.html
--
Fabrízio de Royes Mello
Consultoria/Coaching PostgreSQL
Blog sobre TI: http
arguments... some like this:
\mset vt :table :rows 'select * from :table limit :rows'
Then we can do exactly what you need:
\vt foo 10
\unset vt
I don't know if it's a desired feature but I would love if it exists.
Best regards,
--
Fabrízio de Royes Mello
Consultoria/Coaching PostgreSQL
/CAFcNs+qMGbLmeUOnjmbna_K7=up817bpw9qxhbctgnscpkv...@mail.gmail.com
--
Fabrízio de Royes Mello
Consultoria/Coaching PostgreSQL
Blog sobre TI: http://fabriziomello.blogspot.com
Perfil Linkedin: http://br.linkedin.com/in/fabriziomello
Twitter: http://twitter.com/fabriziomello
or as a student?
As a student.
Regards,
--
Fabrízio de Royes Mello
Consultoria/Coaching PostgreSQL
Blog sobre TI: http://fabriziomello.blogspot.com
Perfil Linkedin: http://br.linkedin.com/in/fabriziomello
Twitter: http://twitter.com/fabriziomello
On Tue, Feb 19, 2013 at 5:43 PM, Heikki Linnakangas hlinnakan...@vmware.com
wrote:
On 19.02.2013 20:07, Fabrízio de Royes Mello wrote:
I would like to propose implement a way to track creation times to
database
objects. This was discussed before in this thread [1].
This was discussed
de Royes Mello
Consultoria/Coaching PostgreSQL
Blog sobre TI: http://fabriziomello.blogspot.com
Perfil Linkedin: http://br.linkedin.com/in/fabriziomello
Twitter: http://twitter.com/fabriziomello
Hi all,
The attached patch fix a little typo on contrib/hstore/crc32.c comment.
Regards,
--
Fabrízio de Royes Mello
Consultoria/Coaching PostgreSQL
Blog sobre TI: http://fabriziomello.blogspot.com
Perfil Linkedin: http://br.linkedin.com/in/fabriziomello
Twitter: http://twitter.com
to be transparent
to the application.
+1
The attached wip patch do that and introduce a subcommand 'SEQUENCES', but
if we decide to don't add a new subcommand to DISCARD, then its easier to
modify the patch.
Regards,
--
Fabrízio de Royes Mello
Consultoria/Coaching PostgreSQL
Blog sobre TI: http
On Fri, Apr 19, 2013 at 11:12 AM, Robert Haas robertmh...@gmail.com wrote:
On Fri, Apr 19, 2013 at 10:05 AM, Fabrízio de Royes Mello
fabriziome...@gmail.com wrote:
The attached wip patch do that and introduce a subcommand 'SEQUENCES',
but
if we decide to don't add a new subcommand
that:
$ bin/psql --variable=FETCH_COUNT=100
psql (9.3devel)
Type help for help.
fabrizio=# \echo :FETCH_COUNT
100
Regards,
[1]
http://www.postgresql.org/docs/current/interactive/app-psql.html#AEN84903
--
Fabrízio de Royes Mello
Consultoria/Coaching PostgreSQL
Blog sobre TI: http
like json, yaml, xml or another one?
Best regards,
--
Fabrízio de Royes Mello
Consultoria/Coaching PostgreSQL
Blog sobre TI: http://fabriziomello.blogspot.com
Perfil Linkedin: http://br.linkedin.com/in/fabriziomello
Twitter: http://twitter.com/fabriziomello
Hi all,
The proposed patch add some files to ignore in .gitignore:
- tags (produced by src/tools/make_ctags)
- TAGS (produced bu src/tools/make_etags)
- .*.swp (may appear in source tree if vi/vim was killed by some reason)
Regards,
--
Fabrízio de Royes Mello
Consultoria/Coaching PostgreSQL
ignore it.
IMHO all output generated by tools inside the source tree that will not be
committed must be added to .gitignore
Regards,
--
Fabrízio de Royes Mello
Consultoria/Coaching PostgreSQL
Blog sobre TI: http://fabriziomello.blogspot.com
Perfil Linkedin: http://br.linkedin.com
and soon I
sent the patch.
Regards,
--
Fabrízio de Royes Mello
Consultoria/Coaching PostgreSQL
Blog sobre TI: http://fabriziomello.blogspot.com
Perfil Linkedin: http://br.linkedin.com/in/fabriziomello
Twitter: http://twitter.com/fabriziomello
create missing objects
and don't
raise an exception if already exists.
Btw., I also want REPLACE BUT DO NOT CREATE.
Can you explain more about it?
Regards,
--
Fabrízio de Royes Mello
Consultoria/Coaching PostgreSQL
Blog sobre TI: http://fabriziomello.blogspot.com
Perfil Linkedin: http
/action/patch_view?id=1133
--
Fabrízio de Royes Mello
Consultoria/Coaching PostgreSQL
Blog sobre TI: http://fabriziomello.blogspot.com
Perfil Linkedin: http://br.linkedin.com/in/fabriziomello
Twitter: http://twitter.com/fabriziomello
://docs.google.com/spreadsheet/ccc?key=0Ai7oCVcVQiKFdEctQUxNNlR1R2xRTUpJNFNDcFo4MUEusp=sharing
--
Fabrízio de Royes Mello
Consultoria/Coaching PostgreSQL
Blog sobre TI: http://fabriziomello.blogspot.com
Perfil Linkedin: http://br.linkedin.com/in/fabriziomello
Twitter: http://twitter.com/fabriziomello
).
[...]
The intention is cover all CREATE OPERATOR variants. See my planning [1].
Regards,
[1]
https://docs.google.com/spreadsheet/ccc?key=0Ai7oCVcVQiKFdEctQUxNNlR1R2xRTUpJNFNDcFo4MUEusp=sharing
--
Fabrízio de Royes Mello
Consultoria/Coaching PostgreSQL
Blog sobre TI: http://fabriziomello.blogspot.com
Perfil
On Thu, Jun 20, 2013 at 9:59 AM, Fabien COELHO coe...@cri.ensmp.fr wrote:
Please fix that and re-send the patch.
Find attached diff wrt current master.
Thanks.
--
Fabrízio de Royes Mello
Consultoria/Coaching PostgreSQL
Blog sobre TI: http://fabriziomello.blogspot.com
Perfil Linkedin
is do that for all CREATE commands.
Regards,
--
Fabrízio de Royes Mello
Consultoria/Coaching PostgreSQL
Blog sobre TI: http://fabriziomello.blogspot.com
Perfil Linkedin: http://br.linkedin.com/in/fabriziomello
Twitter: http://twitter.com/fabriziomello
=0Ai7oCVcVQiKFdEctQUxNNlR1R2xRTUpJNFNDcFo4MUEusp=sharing
--
Fabrízio de Royes Mello
Consultoria/Coaching PostgreSQL
Blog sobre TI: http://fabriziomello.blogspot.com
Perfil Linkedin: http://br.linkedin.com/in/fabriziomello
Twitter: http://twitter.com/fabriziomello
Hi all,
When we run...
./configure --enable-converage
make coverage-html
...the output is generated into /coverage/ directory. The attached patch
add /converage/ to .gitignore.
Regards,
--
Fabrízio de Royes Mello
Consultoria/Coaching PostgreSQL
Blog sobre TI: http
discard to
src/test/regress/parallel_schedule and src/test/regress/serial_schedule,
because if we do make check the new discard test case is not executed.
Regards,
--
Fabrízio de Royes Mello
Consultoria/Coaching PostgreSQL
Blog sobre TI: http://fabriziomello.blogspot.com
Perfil Linkedin: http
missed out: No
- Performance tests required: No
- Any compiler warnings: No
- Are comments sufficient: Yes
- Others: N/A
Regards,
--
Fabrízio de Royes Mello
Consultoria/Coaching PostgreSQL
Blog sobre TI: http://fabriziomello.blogspot.com
Perfil Linkedin: http://br.linkedin.com/in/fabriziomello
=1171
--
Fabrízio de Royes Mello Timbira - http://www.timbira.com.br/
PostgreSQL: Consultoria, Desenvolvimento, Suporte 24x7 e Treinamento
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql
de Royes Mello Timbira - http://www.timbira.com.br/
PostgreSQL: Consultoria, Desenvolvimento, Suporte 24x7 e Treinamento
diff --git a/doc/src/sgml/ref/discard.sgml b/doc/src/sgml/ref/discard.sgml
index 65ebbae..abd3e28 100644
--- a/doc/src/sgml/ref/discard.sgml
+++ b/doc/src/sgml/ref
items off one after the other instead of walking the list
and then NULLing it out at the end. Although no ERROR is possible
here currently, this coding style is generally preferable because it's
robust against being interrupted in the middle.
Thanks!
--
Fabrízio de Royes Mello Timbira
/interactive/fdwhandler.html
--
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
recoveryUntilDelayTime in XLOG_XACT_COMMIT and
XLOG_XACT_COMMIT_COMPACT checks
- don't care about clockdrift because it's an admin problem.
Regards,
[1]
http://www.postgresql.org/message-id/BANLkTi==ttzhdqwzwjdjmof__8yua7l...@mail.gmail.com
--
Fabrízio de Royes Mello
Consultoria/Coaching PostgreSQL
IF NOT EXISTS for all CREATE statements,
including of course the CREATE ROLE statement.
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
- accepting connections
The attached patch fix 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
more work that way. And perhaps that’s for the
best.
I'm planning to implement it for the next commit fest (2014-01)...
Regards,
--
Fabrízio de Royes Mello
Consultoria/Coaching PostgreSQL
Timbira: http://www.timbira.com.br
Blog sobre TI: http://fabriziomello.blogspot.com
Perfil Linkedin
On Wed, Nov 20, 2013 at 2:10 AM, Peter Eisentraut pete...@gmx.net wrote:
On Mon, 2013-11-18 at 11:16 -0200, Fabrízio de Royes Mello wrote:
I'm planning to implement it for the next commit fest (2014-01)...
This email was registered in the commit fest as a patch, but contains no
patch
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-attribute
options.
Regards,
--
Fabrízio de Royes Mello
On Thu, Nov 21, 2013 at 12:05 AM, Robert Haas robertmh...@gmail.com wrote:
On Wed, Nov 20, 2013 at 1:52 PM, Fabrízio de Royes Mello
fabriziome...@gmail.com wrote:
The main goal of this patch is enable to an user the capability to store
options
(relations and attributes) related
] psql-display-all-triggers-v1.patch
http://postgresql.1045698.n5.nabble.com/file/n5775954/psql-display-all-triggers-v1.patch
Hi all,
I'm just send a new WIP patch rebased from master.
Regards,
--
Fabrízio de Royes Mello
Consultoria/Coaching PostgreSQL
Timbira: http://www.timbira.com.br
On Thu, Nov 21, 2013 at 11:06 AM, Robert Haas robertmh...@gmail.com wrote:
On Wed, Nov 20, 2013 at 9:35 PM, Fabrízio de Royes Mello
fabriziome...@gmail.com wrote:
So, with this patch we can do that:
ALTER TABLE foo
SET (ext.somext.do_replicate=true);
When 'ext' is the fixed
,
--
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
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://fabriziomello.blogspot.com
Perfil Linkedin: http://br.linkedin.com/in/fabriziomello
Twitter: http://twitter.com/fabriziomello
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: http://fabriziomello.blogspot.com
Perfil Linkedin: http
customers issues
(has been a crazy week), but I'll reply and/or fix your suggestions later.
Thanks for all review and sorry to delay in reply.
Regards,
--
Fabrízio de Royes Mello
Consultoria/Coaching PostgreSQL
Timbira: http://www.timbira.com.br
Blog sobre TI: http://fabriziomello.blogspot.com
... ;-)
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.blogspot.com
Perfil Linkedin: http://br.linkedin.com/in/fabriziomello
Twitter: http://twitter.com/fabriziomello
diff --git
recovery_time_delay to zero.
I will handle the additional documentation, if you can update the
patch with the main review comments. Thanks.
Thanks, your help is welcome.
Att,
--
Fabrízio de Royes Mello
Consultoria/Coaching PostgreSQL
Timbira: http://www.timbira.com.br
Blog sobre TI: http
On Fri, Dec 6, 2013 at 2:50 AM, Joe Conway m...@joeconway.com 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 the
main suggestion
On Fri, Dec 6, 2013 at 1:36 PM, Robert Haas robertmh...@gmail.com wrote:
On Thu, Dec 5, 2013 at 11:07 PM, Fabrízio de Royes Mello
fabriziome...@gmail.com wrote:
On Tue, Dec 3, 2013 at 5:33 PM, Simon Riggs si...@2ndquadrant.com
wrote:
- compute recoveryUntilDelayTime in XLOG_XACT_COMMIT
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
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://br.linkedin.com/in/fabriziomello
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 code to
avoid
redundancy.
Yep, perhaps something like
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' (functions, variables) to 'standbyDelay'.
Regards,
--
Fabrízio de Royes Mello
Consultoria/Coaching PostgreSQL
Timbira: http
?
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.
Anyway we need to improve docs, any suggestions?
Regards,
--
Fabrízio de Royes Mello
Consultoria/Coaching PostgreSQL
Timbira
here.
Thanks!
--
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 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 si...@2ndquadrant.com
wrote:
On 12 December 2013 15:19, Simon Riggs si...@2ndquadrant.com wrote:
Don't panic guys! I meant UTC offset only. And yes
On Thu, Dec 12, 2013 at 3:11 PM, Pavel Stehule pavel.steh...@gmail.comwrote:
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 PostgreSQL
Timbira
=# 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.com.br
Blog sobre TI: http://fabriziomello.blogspot.com
+, Simon Riggs wrote:
On 12 December 2013 21:58, Fabrízio de Royes Mello
fabriziome...@gmail.com wrote:
Reviewing the committed patch I noted that the
CheckForStandbyTrigger()
after the delay was removed.
If we promote the standby during the delay and don't check
On Fri, Dec 13, 2013 at 3:53 PM, Martijn van Oosterhout klep...@svana.org
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 pavel.steh...@gmail.com
wrote:
Hello
this patch try to complete a set of functions
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 sobre TI: http://fabriziomello.blogspot.com
Perfil Linkedin: http://br.linkedin.com
). 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 patch!
Regards,
--
Fabrízio de Royes Mello
Consultoria/Coaching PostgreSQL
Timbira: http://www.timbira.com.br
Blog sobre TI: http://fabriziomello.blogspot.com
-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
On Tue, Dec 31, 2013 at 9:38 AM, Pavel Stehule pavel.steh...@gmail.com
wrote:
2013/12/31 Fabrízio de Royes Mello fabriziome...@gmail.com
On Tue, Dec 31, 2013 at 9:08 AM, Pavel Stehule pavel.steh...@gmail.com
wrote:
Hello
I am looking on this patch
ALTER TABLE foo SET
On Tue, Dec 31, 2013 at 10:37 AM, Pavel Stehule pavel.steh...@gmail.com
wrote:
2013/12/31 Fabrízio de Royes Mello fabriziome...@gmail.com
On Tue, Dec 31, 2013 at 9:38 AM, Pavel Stehule pavel.steh...@gmail.com
wrote:
2013/12/31 Fabrízio de Royes Mello fabriziome...@gmail.com
On Tue, Dec
. namespaces for relation options.
autovacuum. namespace ???
The HEAP_RELOPT_NAMESPACES (src/include/access/reloptions.h) constant
define only toast and null as a valid relation option namespace.
I missed something?
Regards,
--
Fabrízio de Royes Mello
Consultoria/Coaching PostgreSQL
Timbira
is loaded
2) hack the pg_dump to produce an ALTER TABLE ... SET (...) instead of
CREATE TABLE ... WITH (...) to set reloptions
Comments?
--
Fabrízio de Royes Mello
Consultoria/Coaching PostgreSQL
Timbira: http://www.timbira.com.br
Blog sobre TI: http://fabriziomello.blogspot.com
Perfil
On Wed, Jan 8, 2014 at 8:43 PM, Joshua D. Drake j...@commandprompt.com
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 again?
I vote for Peter.
+1
+1
--
Fabrízio de Royes Mello
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
Timbira: http://www.timbira.com.br
Blog sobre TI: http://fabriziomello.blogspot.com
Perfil Linkedin: http://br.linkedin.com
://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
1 - 100 of 465 matches
Mail list logo
