uses postgresql to think that Login roles does
> not exist. I think it's a bug? or at least a wrong error message
>
I'm not sure. I bet a dime that the role was created as "Iris" and you
are trying to assing "iris" (they are different). If you list the
915,916,917,918,919,920,921,922,923,924,925,926,927,928,929,930,931,932,933,934,935,936,937,938,939,940,941,942,943,944,945,946,947,948,949,950,951,952,953,954,955,956,957,958,959,960,961,962,963,964,965,966,967,968,969,970,971,972,973,974,975,976,977,978,979,980,981,982,983,984,985,986,987,988,989,990,991,992,993,994,995,996,997,998,999,1000
(1 registro)
euler=#
--
Euler Taveira Timbira -
http://www.timbira.com.br/
PostgreSQL: Consultoria, Desenvolvimento, Suporte 24
here.
You didn't write an explicit question but I believe it was your doubt,
didn't it?
--
Euler Taveira Timbira -
http://www.timbira.com.br/
PostgreSQL: Consultoria, Desenvolvimento, Suporte 24x7 e Treinamento
--
Sent via pgsql-hackers mailing list (pg
pport all of the
logical decoding features (for example, origin filter) but it is in my
roadmap.
--
Euler Taveira Timbira -
http://www.timbira.com.br/
PostgreSQL: Consultoria, Desenvolvimento, Suporte 24x7 e Treinamento
--
Sent via pgsql-hackers mai
he old one? +1. It could be
different from the last 3 passwords but we don't store a password
history.
--
Euler Taveira Timbira -
http://www.timbira.com.br/
PostgreSQL: Consultoria, Desenvolvimento, Suporte 24x7 e Treinamento
--
Sent via pgsql-hackers mail
tend pgoutput to support more than one format
(like pglogical did AFAIR), however, we wouldn't reuse code (different
formats) and will have a fat plugin (I don't foresee a plugin using
different formats in the same connection. It is difficult to
coordinate a change like that having
was suggestted that we have a
ready-for-production plugin in core (besides pgoutput). It was
suggested [1] that I submit wal2json for 11. I'm in process to clean
up the code and hope to submit it to CF2.
[1] https://github.com/eulerto/wal2json
[2]
https://www.postgresql.org/me
ements infrastructure, it is possible to create
extensions that prohibit query execution for certain users (see
sql_firewall [1] as an example).
[1] https://github.com/uptimejp/sql_firewall
--
Euler Taveira Timbira -
http://www.timbira.com.br/
Po
plication slot on remote
host as mentioned in section "Replication Slot Management". If we want to
maintain the message let's downgrade it to DEBUG1 (as we do with "create
implicit index for table") but I prefer to rip it out.
--
Euler Taveira T
as is.
Let's leave it as is. At least until 11.
--
Euler Taveira Timbira -
http://www.timbira.com.br/
PostgreSQL: Consultoria, Desenvolvimento, Suporte 24x7 e Treinamento
<http://www.timbira.com.br>
2017-06-16 11:03 GMT-03:00 Peter Eisentraut <
peter.eisentr...@2ndquadrant.com>:
>
>
> Some of that information was sprinkled around, but I have now added a
> new section that collects them all in one place. (section 31.4)
Shouldn't we mention that COPY is supported?
--
f
> the logical replication?
>
Docs stated "Publications can choose to limit the changes they produce to
any combination of INSERT, UPDATE, and DELETE". It is clear that only those
DMLs are supported. However, we should mention that large objects are not
su
out the
> ugliness of specifying refresh twice to disable).
It will cause confusion. It seems that WITH sets ALTER SUBSCRIPTION
properties. Indeed, they are REFRESH properties. I think we shouldn't
exclude REFRESH keyword. Syntax leaves no doubt that WITH are REFRESH
properties.
le would create real tables into information_schema?
Almost zero. Let's leave it alone. Since pg_dump doesn't document that
information_schema isn't dumped, I think we shouldn't document this for
logical replication.
--
Euler Taveira Timbira -
http://www
the command. That's the price we pay to avoid ambiguity that the
previous syntax had.At least I think Petr's proposal is less confusing than
mine (my proposal maintains current behavior but can cause some confusion).
--
Euler Taveira Timbira -
http://www.timbira.com.br/
PostgreSQL: Consultoria, Desenvolvimento, Suporte 24x7 e Treinamento
<http://www.timbira.com.br>
REFRESH WITH (skip = true);
skip (boolean): specifies that the command will not try to refresh table
information. The default is false.
--
Euler Taveira Timbira -
http://www.timbira.com.br/
PostgreSQL: Consultoria, Desenvolvimento, Suporte 24x7 e Treinamento
<http://www.timbira.com.br>
can submit it for the next CF.
[1]
https://www.postgresql.org/message-id/CA%2Bmi_8bJ_uPr67j-6mbin537DVvfk%3DbOhmWneyBRfbZu89q0tw%40mail.gmail.com
--
Euler Taveira Timbira -
http://www.timbira.com.br/
PostgreSQL: Consultoria, Desenvolvimento, Supor
ription sub1 disable;
ALTER SUBSCRIPTION
bar=# drop subscription sub1;
ERROR: could not drop the replication slot "does_not_exist" on publisher
DETAIL: The error was: ERROR: replication slot "does_not_exist" does not
exist
bar=# alter subscription sub1 set (slot_name = NONE);
ALTE
saction.
>
> Is that possible?
>
> If so, can you please provide an example or point me into the right
> direction?
>
>
>
Take a look at BDR code (bdr_queue_ddl_commands and
bdr_queue_dropped_objects) [1]. It implements DDL replication too.
[1] https://github.com/2ndQuad
2017-04-19 1:32 GMT-03:00 Michael Paquier <michael.paqu...@gmail.com>:
> I vote for "location" -> "lsn". I would expect complains about the
> current inconsistency at some point, and the function names have been
> already changed for this r
Taveira Timbira -
http://www.timbira.com.br/
PostgreSQL: Consultoria, Desenvolvimento, Suporte 24x7 e Treinamento
<http://www.timbira.com.br>
From da4dc2807566958dd89cc9f05bf6a83a996e99c7 Mon Sep 17 00:00:00 2001
From: Euler Taveira <eu...@timbira.com
Both in tablesync and
> in DoCopy instead of the old coding.
>
Patch works fine. However, I don't see any documentation about supporting
different schemas for logical replication. Is it an oversight?
--
Euler Taveira Timbira -
http://www.timbira.com.br/
?
--
Euler Taveira Timbira -
http://www.timbira.com.br/
PostgreSQL: Consultoria, Desenvolvimento, Suporte 24x7 e Treinamento
<http://www.timbira.com.br>
e from. You can
check for duplicates with a small script.
--
Euler Taveira Timbira - http://www.
timbira.com.br/
PostgreSQL: Consultoria, Desenvolvimento, Suporte 24x7 e Treinamento
<http://www.timbira.com.br>
d reindexdb).
[1]
https://www.postgresql.org/message-id/bdd1adb1-c26d-ad1f-2f15-cc5205606...@timbira.com.br
--
Euler Taveira Timbira -
http://www.timbira.com.br/
PostgreSQL: Consultoria, Desenvolvimento, Suporte 24x7 e Treinamento
<http://www.timbira.com.br>
act member wraparound
> protections are now enabled
>
It should be DEBUG1 as soon as 9.3 is deprecated.
> 2017-03-09 23:40:12.335 EST [19339] LOG: autovacuum launcher started
> 2017-03-09 23:40:12.336 EST [19341] LOG: logical replication launcher
> started
>
ersion routines.
--
Euler Taveira 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-hackers
Of
course, it should be documented. Also, if someone wants to replicate an
information schema table, it could do it with ALTER PUBLICATION.
--
Euler Taveira Timbira - http://www.timbira.com.br/
PostgreSQL: Consultoria, Desenvolvimento, Suporte 24x7 e Treinamento
--
S
clean up this code. Let's do it smoothly.
As Robert suggested in the other email: extension to create old names.
--
Euler Taveira Timbira - http://www.timbira.com.br/
PostgreSQL: Consultoria, Desenvolvimento, Suporte 24x7 e Treinamento
--
Sent via pgsql-hackers mailin
On 11-01-2017 21:29, Josh Berkus wrote:
> For that reason, as of today, I am stepping down from the PostgreSQL
> Core Team.
>
Thanks for your hard work! Your contributions were very important and
valuable for community growth. I'm sure you will continue to advocate
PostgreSQL.
--
hing the complete and also a patch at the top of your last patch.
--
Euler Taveira Timbira - http://www.timbira.com.br/
PostgreSQL: Consultoria, Desenvolvimento, Suporte 24x7 e Treinamento
diff --git a/doc/src/sgml/func.sgml b/doc/src/sgml/func.sgml
index 10e3186..1e52a48
ick with a default value that could not be a
good idea in the security pov).
--
Euler Taveira 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 c
log_replay_location
> pg_is_xlog_replay_paused
> pg_switch_xlog
> pg_xlog_replay_pause
> pg_xlog_replay_resume
> (12 rows)
>
In those cases, let's keep the functions as wrappers and undocumented.
In a few releases, we could remove them without breaking softwares that
r
wise >=.
There could be TAP tests for pg_recvlogical but it is material for
another patch.
I'll mark this patch waiting on author for your considerations.
--
Euler Taveira Timbira - http://www.timbira.com.br/
PostgreSQL: Consultoria, Desenvolvimento, Suporte 24x7 e Tre
On 26-10-2016 12:43, Serge Rielau wrote:
> Posting to this group on a Friday evening was obviously a Bad Idea(tm). :-)
>
Serge, add your patch to the next commitfest [1] so we don't forget to
review it.
[1] https://commitfest.postgresql.org/11/
--
Euler Taveira T
[1]
https://www.postgresql.org/message-id/3073cc9b0910051618t693d15f3u265872908240d...@mail.gmail.com
--
Euler Taveira Timbira - http://www.timbira.com.br/
PostgreSQL: Consultoria, Desenvolvimento, Suporte 24x7 e Treinamento
--
Sent via pgsql-hackers mailing list (pgs
> above between instance-wide and db-specific holds.
>
I don't use it for a long time. It also a client-side binary then better
place for it is pg_command. BTW, is anybody using it? If so, we could
add this functionality to psql and remove it.
--
Euler Taveira
.
Opinions?
--
Euler Taveira 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
heir cluster, because they are just *logs*.
>
> ...and we also have "pg_logical", that includes a "log" keyword already...
>
"clog" and "xlog" is almost "log"; "logical" is not. I don't imagine
people confusing "logic
a third parameter (say, validate = true | false)
instead of creating another function? The new parameter could default to
false to not break compatibility.
--
Euler Taveira Timbira - http://www.timbira.com.br/
PostgreSQL: Consultoria, Desenvolvimento, Suporte 24x7 e Trei
e run during downtime, so it seems like you'd
> want those to run as fast as possible.
>
Doesn't --new-options do the job?
--
Euler Taveira Timbira - http://www.timbira.com.br/
PostgreSQL: Consultoria, Desenvolvimento, Suporte 24x7 e Treinamento
--
Sent via pgs
gt; min(citext)
> max(citext)
> int_array_aggregate(int4)
> rewrite(tsquery[])
>
I don't think those functions are used a lot (as you said) to justify
adding more code in 9.6. Let's not be in a hurry on something that can
wait some months.
--
Euler Taveira Ti
I'm all ears.
--
Euler Taveira 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-hackers
On 10-05-2016 22:22, David G. Johnston wrote:
> I don't know how the docs, this function, and the source code relate to
> each other.
>
Function is built around ScanKeywords structure which in turn is built
using parser/kwlist.h.
--
Euler Taveira Timbi
6 | t| t
6 | NULL | f| NULL
NULL |3 | f| NULL
NULL |6 | f| NULL
NULL | NULL | t| NULL
(9 rows)
--
Euler Taveira Timbira - http://www.timbira.com.br/
PostgreSQL: Consultoria, Desenvolvimento, Suporte 24x7 e Treinamento
--
Sent
is a hack
and must be done with care.
--
Euler Taveira 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
could also try oprname, oprrest or oprjoin but the result
is worse than the former solution. You definitely need a hack.
Also, IS DISTINCT FROM is an alias for = operator per standard IIRC.
--
Euler Taveira Timbira - http://www.timbira.com.br/
PostgreSQL: Consultoria, Desenvolvime
lators [2] to send corrections / translations.
[1] http://git.postgresql.org/gitweb/?p=pgtranslation/messages.git;a=summary
[2] http://www.postgresql.org/list/pgsql-translators/
--
Euler Taveira Timbira - http://www.timbira.com.br/
PostgreSQL: Consultoria, Desenvolvimento, Suporte
On 07-05-2016 22:53, Robins Tharakan wrote:
> Should I be looking somewhere else? Parse keywords from Git Source file
> (if so where)? Parse PG Documentation?
>
src/include/parser/kwlist.h
--
Euler Taveira Timbira - http://www.timbira.com.br/
PostgreSQL: Co
file exists"
Attached is a patch that turn it into one.
--
Euler Taveira Timbira - http://www.timbira.com.br/
PostgreSQL: Consultoria, Desenvolvimento, Suporte 24x7 e Treinamento
diff --git a/src/backend/access/transam/xlog.c b/src/backend/access/transam/xlog.c
in
o pass timeline information "around" the walsender and
> share more of the logic between the code paths.
>
Question is: is the actual code so useless that it can't even be a 1.0
release? A lot of (complex) features were introduced with the notion
that will be improved in the ne
do some POC
with LZ compression (that is already available in common).
I'll try to update the code and do some benchmarks.
[1] http://www.postgresql.org/message-id/4fd9698f.2090...@timbira.com
--
Euler Taveira Timbira - http://www.timbira.com.br/
PostgreSQL: Consultor
ould be sufficient.
--
Euler Taveira 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.postg
nditional
expression into a variable.
+ if (isDelete ? t->oprnegate == baseId : !OidIsValid(t->oprnegate))
It could be separate into a variable to be readable (or at least deserve
a comment).
(isDelete ? InvalidOid : ObjectIdGetDatum(baseId))
... and this one too. It is used in 4 place
t;
Those are good concerns. Also, we already have emit_log_hook that could
grab server log messages. A small extension using the hook (there are
some out there) could be use with a log consuming tool.
--
Euler Taveira Timbira - http://www.timbira.com.br/
PostgreSQL: C
patterns and you can also use
syslog for it.
--
Euler Taveira 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
cumstances (and even discard
some messages).
--
Euler Taveira 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
most common values I use for c_t).
--
Euler Taveira 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:
h
On 26-01-2016 09:53, Michael Paquier wrote:
> Something like the patch attached would be fine? This wins a backpatch
> because the query continuously running eats memory, no?
>
+1. Although it breaks compatibility, a function that just eats
resources is not correct.
--
Eule
.
>
3. Add a WARNING at startup (until removal of values) saying something
like "'archive' value is deprecated and will be removed in a future
version. Use 'replica' value instead."
--
Euler Taveira Timbira - http://www.timbira.com.br/
PostgreSQL: Con
I think you don't understand the point: start with the *right* cmake
version because you could have to redo (a lot of) your work or have your
patch rejected because you don't follow our advice.
--
Euler Taveira Timbira - http://www.timbira.com.br/
PostgreSQL: Consultori
On 26-11-2015 07:33, YUriy Zhuravlev wrote:
> On Thursday 26 November 2015 01:29:37 Euler Taveira wrote:
>> I give it a try. Nice WIP. IMHO you should try to support cmake version
>> that are available in the stable releases. Looking at [1], I think the
>> best choi
ngs to repository. If someone wants to develop
a patch, we should advice him/her to use git.
+1 to remove all of those files.
--
Euler Taveira Timbira - http://www.timbira.com.br/
PostgreSQL: Consultoria, Desenvolvimento, Suporte 24x7 e Treinamento
--
Sent via pgsql-hac
will cover Red Hat based distros and
also Debian based ones). Are you using a new feature from 3.1? I mean,
it should be nice to cover old stable releases, if it is possible.
[1] https://cmake.org/Wiki/CMake_Life_Cycle_Considerations
--
Euler Taveira Timbira - http://www.timbi
On 07-11-2015 12:21, Praveen M wrote:
I would like to print the raw parse tree into the log . Is there any
internal utility function to achieve this. If there is none , can you
please help me to achieve this.
debug_print_parse = on
--
Euler Taveira Timbira - http
in -bugs because the discussion started
there. Sometimes people track -bugs ML to make sure that some bugs
aren't forgotten. Add your patch to the next CF [1].
[1] https://commitfest.postgresql.org/7/
--
Euler Taveira Timbira - http://www.timbira.com.br/
PostgreSQL
start of regular streaming
replication.
Reviewed-by: Michael Paquier <michael.paqu...@gmail.com>
--
Euler Taveira Timbira - http://www.timbira.com.br/
PostgreSQL: Consultoria, Desenvolvimento, Suporte 24x7 e Treinamento
--
Sent via pgsql-hackers maili
On 21-10-2015 18:36, Andres Freund wrote:
On 2015-10-21 11:52:31 -0300, Euler Taveira wrote:
While testing wal2json, I faced some problems with pg_recvlogical. Attached
is a serie of patches that can improve pg_recvlogical. Patches #2 and #3 are
bugfixes (and should be applied to 9.5 too
On 20-10-2015 08:28, Bernd Helmle wrote:
The 2nd assignment to slot_name looks unnecessary?
Yes, it is. Seems to be an oversight. Patch attached.
--
Euler Taveira Timbira - http://www.timbira.com.br/
PostgreSQL: Consultoria, Desenvolvimento, Suporte 24x7 e Treinamento
);
--
Euler Taveira Timbira - http://www.timbira.com.br/
PostgreSQL: Consultoria, Desenvolvimento, Suporte 24x7 e Treinamento
>From 9b3d63d1744e2b65a7f1a1d44ed166f4c9684771 Mon Sep 17 00:00:00 2001
From: Euler Taveira <eu...@timbira.com.br>
Date: Tue, 1 Sep 2015
entry in pg_hba.conf.
[1] http://www.postgresql.org/docs/current/static/auth-methods.html#AUTH-PAM
[2] http://www.postgresql.org/docs/current/static/role-membership.html
--
Euler Taveira Timbira - http://www.timbira.com.br/
PostgreSQL: Consultoria, Desenvolvimento, Suporte
ter on it.
[1] http://pubs.opengroup.org/onlinepubs/8329799/pam_set_item.htm
--
Euler Taveira Timbira - http://www.timbira.com.br/
PostgreSQL: Consultoria, Desenvolvimento, Suporte 24x7 e Treinamento
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
n. I'm not a PAM expert but my impression is that rhost is an optional
item. Therefore, advise PAM users to use HBA is a way to not complicate
the actual feature.
--
Euler Taveira Timbira - http://www.timbira.com.br/
PostgreSQL: Consultoria, Desenvolvimento, Suporte 24x7 e Trein
On 06-10-2015 19:49, Andreas 'ads' Scherbaum wrote:
When working on a script, I stumbled over a mistake in the pt_BR.po
translation for ecpg. Patch attached.
I've already fixed it in the translation git. It'll be available only in
the next set of releases.
--
Euler Taveira
On 07-10-2015 14:05, Alvaro Herrera wrote:
Euler Taveira wrote:
On 06-10-2015 19:49, Andreas 'ads' Scherbaum wrote:
When working on a script, I stumbled over a mistake in the pt_BR.po
translation for ecpg. Patch attached.
I've already fixed it in the translation git. It'll be available only
E command (emitted if a parameter was informed)
during dump could handle it. BTW, last thread [1] about logical column
ordering seems to have died a few months ago. Alvaro?
[1]
http://www.postgresql.org/message-id/20141209174146.gp1...@alvh.no-ip.org
--
Euler Taveira Tim
On 17-09-2015 00:25, Fujii Masao wrote:
One relevant question is; why doesn't pg_controldata report newestCommitTs?
I thought about it while looking at the code but forgot to ask. AFAICS
it is an oversight. See attached patch.
--
Euler Taveira Timbira - http
On 18-09-2015 00:59, Amit Kapila wrote:
On Fri, Sep 18, 2015 at 8:30 AM, Euler Taveira <eu...@timbira.com.br
<mailto:eu...@timbira.com.br>> wrote:
>
> Hi,
>
> Is there a reason to quote "jobs" at this sentence?
>
> 190 fprintf(stderr, _("%s: num
ssage a few lines above (correctly) does not
use quotes.
--
Euler Taveira 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
Hi,
This simple patch improves a sentence. Spotted while working on translation.
--
Euler Taveira Timbira - http://www.timbira.com.br/
PostgreSQL: Consultoria, Desenvolvimento, Suporte 24x7 e Treinamento
>From 7cae997155e222e0a8280018cccf717ab2ee1c38 Mon Sep 17 00:00
On 16-09-2015 10:57, Tom Lane wrote:
Euler Taveira <eu...@timbira.com.br> writes:
This simple patch improves a sentence. Spotted while working on translation.
I concur that spelling out "#" as "number" is an improvement, but I'm
curious which backend error you think
. Patch is attached. It is new in 9.5 so backpatch is needed.
--
Euler Taveira Timbira - http://www.timbira.com.br/
PostgreSQL: Consultoria, Desenvolvimento, Suporte 24x7 e Treinamento
>From cc8da654ab363366860de6c114bfc9a28561978a Mon Sep 17 00:00:00 2001
From: Eu
superuser-only?
pg_recovery_config(OUT name text, OUT setting text) SETOF record
or
pg_recovery_config(OUT name text, OUT setting text, IN all bool) SETOF
record
This function covers pg_standby_conninfo().
--
Euler Taveira Timbira - http://www.timbira.com.br/
PostgreSQL
Hi,
Attached is a small typo.
--
Euler Taveira Timbira - http://www.timbira.com.br/
PostgreSQL: Consultoria, Desenvolvimento, Suporte 24x7 e Treinamento
diff --git a/contrib/pg_buffercache/pg_buffercache_pages.c b/contrib/pg_buffercache/pg_buffercache_pages.c
index
. With things like systemd, launchd, supervisord that like to
manage the daemons directly, using postgres directly might be the
preferable choice.
Agree. However, I'm saying that _general users_ (those that don't use OS
init interface) tend to prefer 'pg_ctl' to 'postgres'.
--
Euler Taveira
/debugging purposes. None of
those use cases are intended for general users. Let's make it simple and
drop 'postgres' line.
--
Euler Taveira Timbira - http://www.timbira.com.br/
PostgreSQL: Consultoria, Desenvolvimento, Suporte 24x7 e Treinamento
--
Sent via pgsql
and found some low-hanging fruit.
--
Euler Taveira Timbira - http://www.timbira.com.br/
PostgreSQL: Consultoria, Desenvolvimento, Suporte 24x7 e Treinamento
From 3ce5376868f61a67540915b83a15c59a31fc895a Mon Sep 17 00:00:00 2001
From: Euler Taveira eu...@timbira.com
Date: Sun, 26
to follow the default postgresql.conf.
They don't add or remove parameters but replace values.
--
Euler Taveira Timbira - http://www.timbira.com.br/
PostgreSQL: Consultoria, Desenvolvimento, Suporte 24x7 e Treinamento
--
Sent via pgsql-hackers mailing list (pgsql-hackers
in spanish and client
messages in french. Is it an acceptable plan? Ideas?
--
Euler Taveira Timbira - http://www.timbira.com.br/
PostgreSQL: Consultoria, Desenvolvimento, Suporte 24x7 e Treinamento
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org
Hi,
The pg_recvlogical docs was rewritten but someone forgot to tweak the
help description. It is a bit late in the 9.4 cycle but let be consistent.
Regards,
--
Euler Taveira Timbira - http://www.timbira.com.br/
PostgreSQL: Consultoria, Desenvolvimento, Suporte 24x7 e
Hi,
I noticed that a setting in pg_settings without units have NULL and
as unit values ( for integer and NULL for the other ones). Could we be
consistent? It is like that since units were introduced (b517e65). No
unit means unit = NULL. A proposed patch is attached.
--
Euler Taveira
/README.
--
Euler Taveira 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
.
--
Euler Taveira 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-hackers
be an alternative to pg_upgrade.
--
Euler Taveira 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
Hi,
Here are some more trivial fixes in pg_recvlogical message style.
--
Euler Taveira Timbira - http://www.timbira.com.br/
PostgreSQL: Consultoria, Desenvolvimento, Suporte 24x7 e Treinamento
From 0bbf437b490a92afa4b14e4903188bcf795f8e47 Mon Sep 17 00:00:00 2001
From
the walsender interface that's not covered by any
tests right now...
beta is not the right time to add even a *minor* functionality. Let's do
it for 9.5.
--
Euler Taveira Timbira - http://www.timbira.com.br/
PostgreSQL: Consultoria, Desenvolvimento, Suporte 24x7 e
Hi,
While updating pt-br translation I noticed that some sentences could be
improved. I also fix some style glitches. A set of patches are attached.
--
Euler Taveira Timbira - http://www.timbira.com.br/
PostgreSQL: Consultoria, Desenvolvimento, Suporte 24x7 e
') and just one view.
--
Euler Taveira 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
it will be removed soon.
--
Euler Taveira 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
of validating things.
euler@euler=# reset noname;
ERROR: 42704: unrecognized configuration parameter noname
LOCAL: set_config_option, guc.c:5220
--
Euler Taveira Timbira - http://www.timbira.com.br/
PostgreSQL: Consultoria, Desenvolvimento, Suporte 24x7 e Treinamento
--
Sent
1 - 100 of 437 matches
Mail list logo