;
We don't normally add new features to stable branches unless it is a bug. In
the optimizer case, planner regression is a bug (that this case is not).
--
Euler Taveira de Oliveira - Timbira http://www.timbira.com.br/
PostgreSQL: Consultoria, Desenvolvimento, Suporte 24x7 e
On 29-02-2012 15:23, Thom Brown wrote:
> Or just change it to output a verbose notice without changing the syntax?
>
I can't see why we will do it only for DROP OWNED. Chat messages are annoying
unless the user asks for it (that's why I suggested VERBOSE).
--
Euler Tav
On 29-02-2012 14:20, Thom Brown wrote:
> No, the cascade part is fine. It's the objects which won't cause a
> cascade that are an issue. Putting it in a transaction for rolling
> back doesn't help find out what it intends to drop.
>
DROP OWNED BY foo VERBOSE?
--
something obvious?
>
sscanf() is too fragile for input sanity check. Try
pg_xlog_location_diff('12/3', '-10/0'), for example. I won't object removing
that function if you protect xlog location input from silly users.
--
Euler Taveira de Oliveira - Timbira
g/docs/devel/static/rangetypes.html
--
Euler Taveira de Oliveira - 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.post
t;wrap around"?
In this case, we have an idea that wal_buffers needs to be increased.
--
Euler Taveira de Oliveira - Timbira http://www.timbira.com.br/
PostgreSQL: Consultoria, Desenvolvimento, Suporte 24x7 e Treinamento
--
Sent via pgsql-hackers mailing list (pgsql-hackers@po
#x27;ll not attach another version for pg_size_pretty because it is a matter of
updating a duplicated OID.
--
Euler Taveira de Oliveira - 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/f
etty(numeric). It is slower than the former but it is not a
performance critical function.
> According to the above source code comment in pg_proc.h, ISTM
> pg_size_pretty() for numeric also needs to have its own DESCR().
>
Fixed.
> According to "man strcat", the dest stri
ackup copies are
running. As about returning the backup timestamp, we could return an array
like array[['label_1', '2012-01-28 02:00:01 BRST'], ['label_2', '2012-01-28
03:40:34 BRST']] or NULL if none.
--
Euler Taveira de Oliveira - Timbira h
your patch
to the next CF.
--
Euler Taveira de Oliveira - 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.pos
I couldn't. I attached another patch that implements
pg_size_pretty(numeric).
--
Euler Taveira de Oliveira - 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 4863
it.
I'll post this weekend.
--
Euler Taveira de Oliveira - 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 subs
On 13-01-2012 18:50, Josh Berkus wrote:
> It occurs to me that I would find it quite personally useful if the
> vacuumdb utility was multiprocess capable.
>
It is in the mid of my TODO list. reindexdb is in the plans too.
--
Euler Taveira de Oliveira - Timbira
0048
>
What about just 'restored log file "00080048" from pg_xlog'
instead of the last two messages? If you can't read from pg_xlog emit 'could
not restore file "00080048" from pg_xlog'.
--
Euler Taveira de Oliv
On 20-12-2011 07:27, Magnus Hagander wrote:
> On Tue, Dec 6, 2011 at 19:06, Robert Haas wrote:
>> On Tue, Dec 6, 2011 at 1:00 PM, Euler Taveira de Oliveira
>> wrote:
>>> On 06-12-2011 13:11, Robert Haas wrote:
>>>> On Tue, Dec 6, 2011 at 5:14 AM, Magnus Ha
of both installations?
--
Euler Taveira de Oliveira - 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
far. If so, you want to change
all of those functions that deal with LSNs and add some implicit conversion
between text and lsn data types (for backward compatibility). As of int8, I'm
not aware of any modern plataform that int8 is not 64 bits. I'm not against
numeric use; I'
On 06-12-2011 07:14, Magnus Hagander wrote:
> On Tue, Dec 6, 2011 at 05:19, Euler Taveira de Oliveira
> wrote:
>> Hi,
>>
>> A while ago when blogging about WAL [1], I noticed a function to deal with
>> xlog location arithmetic is wanted. I remembered Depez [2] m
/2011/01/24/waiting-for-9-1-pg_stat_replication/
--
Euler Taveira de Oliveira - 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 ddfb29a..cce218a 100644
--- a/doc
dations. If (s)he mistyped the name of the file, the general
recommendations will not be applied and the DBA won't be even warned. That's
not what a DBA would expect.
--
Euler Taveira de Oliveira - Timbira http://www.timbira.com.br/
PostgreSQL: Consultoria, Desenvolvimento,
n mind that a
symmetric functionality (e.g. on-logoff hook or on-disconnect trigger) should
be implemented too.
--
Euler Taveira de Oliveira - Timbira http://www.timbira.com.br/
PostgreSQL: Consultoria, Desenvolvimento, Suporte 24x7 e Treinamento
--
Sent via pgsql-hackers mailing l
activity frequently.
--
Euler Taveira de Oliveira - 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
etter than
nothing. If we decided to improve this area in a future we should remove the
warning but right now it would be an excelent hint to tune autovacuum.
[1] http://archives.postgresql.org/pgsql-hackers/2011-06/msg00678.php
--
Euler Taveira de Oliveira - Timbira
On 24-10-2011 11:36, Tom Lane wrote:
Euler Taveira de Oliveira writes:
The main point of autovacuum is maintenance tasks. Currently, it executes
VACUUM and ANALYZE commands. I want to propose that we incorporate vacuumlo
functionality into it.
I'm not terribly thrilled with that becau
e its reference at
the same database. Yes, it is a possibility but ...
--
Euler Taveira de Oliveira - 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
orphaned LO be cleaned up by VACUUM
but that a history for another thread...
Comments?
--
Euler Taveira de Oliveira - Timbira http://www.timbira.com.br/
PostgreSQL: Consultoria, Desenvolvimento, Suporte 24x7 e Treinamento
--
Sent via pgsql-hackers mailing list (pgsql-hackers
is GUC can only be changed by superuser.
--
Euler Taveira de Oliveira - 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 sub
I could do that, if I had the exact procedure... Currently,
during the start of the backup I take the following information:
Just show us the output of pg_start_backup and part of the standby log with
the following message 'redo starts at' and the subsequent messages up to the
failure.
On 22-09-2011 12:39, Daniel Vázquez wrote:
Before 9.x, how do unaccent full text searches ?
Perform pre-processing (normalization) of the string *before* inserting and
*before* searching.
--
Euler Taveira de Oliveira - Timbira http://www.timbira.com.br/
PostgreSQL: Consultoria
On 21-09-2011 15:23, Daniel Vázquez wrote:
No alternatives for unaccent on 8.4?
Not that I know of.
--
Euler Taveira de Oliveira - Timbira http://www.timbira.com.br/
PostgreSQL: Consultoria, Desenvolvimento, Suporte 24x7 e Treinamento
--
Sent via pgsql-hackers mailing list
On 21-09-2011 13:28, Daniel Vázquez wrote:
"unaccent" is compatible with postgresql 8.4 (but not is in their contrib
version distribution)
No, it is not. AFAICS it is necessary to add some backend code that is not in
8.4.
--
Euler Taveira de Oliveira - Timbira
instance.
The last step will, usually, fail with a similar error:
The problem could be that the minimum recovery point (step 2.3) is different
from the end of rsync if you are under load.
--
Euler Taveira de Oliveira - Timbira http://www.timbira.com.br/
PostgreSQL: Consultoria, Dese
http://www.postgresql.org/docs/current/static/maintenance.html
--
Euler Taveira de Oliveira - 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 subscri
lar topics, they could contact you
and get involved.
Of course it is. I just not wanted to spam hackers.
But if it is community interest, of course it will bother no one here...
--
Euler Taveira de Oliveira - Timbira http://www.timbira.com.br/
PostgreSQL: Consultoria, Desen
_mode) or a file (say recovery -> recovery.done). Also, recovery.done
could be filled with recovery information just for DBA record. standby_mode
does not create any file, it just trigger the recovery (as it will be used
mainly for replication purposes).
--
Euler Taveira
Hi,
While updating the translation I noticed a typo in
src/backend/commands/collationcmds.c circa line 126.
parameter \"lc_collate\" parameter must be specified
--
Euler Taveira de Oliveira - Timbira http://www.timbira.com.br/
PostgreSQL: Consultoria, Desenvolvimento, Su
Em 24-08-2011 11:27, Tom Lane escreveu:
Hmm. I agree we need to avoid executing 0/0 here, but should we force
the result to 0, or to NaN?
If it returns NaN on other platforms, let's be consistent.
--
Euler Taveira de Oliveira - Timbira http://www.timbira.com.br/
Postg
cover the maintenance activity. This new view
could contain at least datname, schemaname, relname, command_start,
command_schedule, operation, progress (?), procpid, and current_command. The
name has to be generic to cover all maintenance commands (perhaps
pg_maintenance_activity).
--
Euler
Hi,
While looking at Greg's patch I spotted that resource usage code for vacuum is
initialized even if we won't use it. Attached is a small patch that moves it
to the right place (this code mimics do_analyze_rel function).
--
Euler Taveira de Oliveira - Timbira
ow do you handle it?
It would be another patch... autovacuum has an option to display summarized
information but vacuum don't. Isn't it time to be symmetrical here?
--
Euler Taveira de Oliveira - Timbira http://www.timbira.com.br/
PostgreSQL: Consultoria, Desenvolvimento,
ttp://archives.postgresql.org/pgsql-hackers/2011-06/msg00678.php
--
Euler Taveira de Oliveira - 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
r counters easier to implement and simpler to
analyze. But the timestamp idea has its merit because we already have a
similar statistic (last timestamp table was vacuumed or analyzed).
--
Euler Taveira de Oliveira - Timbira http://www.timbira.com.br/
PostgreSQL: Consultoria, Desenvolvim
me to split autovacuum information into another statistic view?
Comments?
--
Euler Taveira de Oliveira - Timbira http://www.timbira.com.br/
PostgreSQL: Consultoria, Desenvolvimento, Suporte 24x7 e Treinamento
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To
Em 07-05-2011 13:42, Peter Eisentraut escreveu:
Do you need pg_config to install extensions?
No. But we need it to build other extensions.
--
Euler Taveira de Oliveira - Timbira http://www.timbira.com.br/
PostgreSQL: Consultoria, Desenvolvimento, Suporte 24x7 e Treinamento
--
Sent
.
>
I'm in favor of find out what are the popular extensions and make them into
"base"; the other ones could be moved to PGXN.
--
Euler Taveira de Oliveira - Timbira http://www.timbira.com.br/
PostgreSQL: Consultoria, Desenvolvimento, Suporte 24x7 e Treinamento
--
need to change the code to achieve what
you want.
--
Euler Taveira de Oliveira - 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
27;make world' is not the answer. There is not an option for "install
all pieces of software". Let's install pg+contrib and leave only 'CREATE
EXTENSION foo' for the admins.
--
Euler Taveira de Oliveira - Timbira http://www.timbira.com.br/
PostgreSQL: C
hanges and case-folding changes in just one
single-byte encoding --- anybody?
ISO-8859-9?
I'm afraid we have to map lang to single byte character set. Not all languages
prefer ISO-8859.
--
Euler Taveira de Oliveira
http://www.timbira.com/
--
Sent via pgsql-hackers mailing
some cases. IIRC the comments are not there to avoid
bloating the catalog. One month ago or so I saw a commit to comment operator
support functions. Maybe it is worth comment system catalog too [1].
[1] http://eulerto.blogspot.com/2010/11/comment-on-catalog-tables.html
--
Euler Tavei
l/foo and search for foo_call_handler function (it is the entry
point).
--
Euler Taveira de Oliveira
http://www.timbira.com/
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
Em 28-02-2011 15:50, Tom Lane escreveu:
Ultimately we need to think of a reporting mechanism that's a bit
smarter than "rewrite the whole file for any update" ...
What about splitting statistic file per database?
--
Euler Taveira de Oliveira
http://www.timbira.com/
--
time they occurred?
Good point. I included location instead of time; time is already supplied by
log file.
The following patch implements the Thom's suggestions.
[1] http://archives.postgresql.org/message-id/4d48209c.7050...@timbira.com
--
Euler Taveira de Oliveira
http://www.ti
resql.org/message-id/e4ccc24e0810222010p12bae2f4xa3a11cb2bc51bd89%40mail.gmail.com
--
Euler Taveira de Oliveira
http://www.timbira.com/
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
transaction or time." Why?
Because named restore point is a noop xlog record; besides, transaction and
time involves xlog records that contain data.
--
Euler Taveira de Oliveira
http://www.timbira.com/
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
Em 06-02-2011 13:09, Bruce Momjian escreveu:
What happened to this idea/patch?
I refactored the patch [1] to not depend on strtoll.
[1] http://archives.postgresql.org/message-id/4d2cccd9@timbira.com
--
Euler Taveira de Oliveira
http://www.timbira.com/
--
Sent via pgsql-hackers
ting on author because of those open issues.
This patch needs to bump catalog version because of the new function. I'm not
sure if the new record type requires bumping the xlog magic number.
I'm attaching the updated patch and two scripts that I used to play with the
patch.
Em 21-01-2011 12:47, Andrew Dunstan escreveu:
Maybe we could change the hint to say "--file=DESTINATION" or
"--file=FILENAME|DIRNAME" ?
... "--file=OUTPUT" or "--file=OUTPUTNAME".
--
Euler Taveira de Oliveira
http://www.timbira.com/
--
Sent via p
t mark it "ready
for committer" instead leave it as is ("needs review"); just be sure to add
your comments in the commitfest app.
[1] http://wiki.postgresql.org/wiki/RRReviewers
--
Euler Taveira de Oliveira
http://www.timbira.com/
--
Sent via pgsql-hackers mailing
't be hard to do..)
+1.
--
Euler Taveira de Oliveira
http://www.timbira.com/
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
Em 14-01-2011 19:50, Jaime Casanova escreveu:
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 an
h. I personally
would like to eyeball his patch (but it will be during the week).
--
Euler Taveira de Oliveira
http://www.timbira.com/
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
y point as '1234567' (xid) or '2011-01-14' (I use this format
a lot) and (ii) if the suffix name is *_name* it shouldn't allow xid and time.
IMHO, recovery_target_name should allow only names.
--
Euler Taveira de Oliveira
http://www.timbira.com/
--
Sent via pgsql-
Em 10-01-2011 05:25, Greg Smith escreveu:
Euler Taveira de Oliveira wrote:
Em 07-01-2011 22:59, Greg Smith escreveu:
setrandom: invalid maximum number -2147467296
It is failing at atoi() circa pgbench.c:1036. But it just the first
one. There are some variables and constants that need to be
an states (in normal scenarios).
--
Euler Taveira de Oliveira
http://www.timbira.com/
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
Em 06-01-2011 21:31, Tom Lane escreveu:
I think I like option #2 better. Comments?
+1.
--
Euler Taveira de Oliveira
http://www.timbira.com/
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref
fulfill people's desire that
claim an easy replication setup.
IIRC, Dimitri already coded a base backup over libpq tool [1] but it is
written in Python.
[1] https://github.com/dimitri/pg_basebackup/
--
Euler Taveira de Oliveira
http://www.timbira.com/
--
Sent via pgsql-hackers ma
aaliya zarrin escreveu:
> I want to signal the postmaster (User defined signal) once I created the
> trigger file (for switch over).
>
Send a SIGHUP to postmaster. Have in mind that it doesn't work on all
supported platforms.
--
Euler Taveira de Oliveira
http://www.timbira.
that a signal doesn't wake up a
process, so I suggest (ii) but I'm fine to include (i) at docs too.
Comments?
[1]
http://git.postgresql.org/gitweb?p=postgresql.git;a=commitdiff;h=723d0184e2972f21db0f85feef3d35f0cb9b3298
--
Euler Taveira de Oliveira
http://www.timbira.com/
oking at the manual but the -o
option only accept initdb options so I think there is a documentation bug.
Patch is attached.
While at it, is it worth adding a pg_ctl init example?
--
Euler Taveira de Oliveira
http://www.timbira.com/
diff --git a/doc/src/sgml/ref/pg_ctl-ref.sgml b/doc/src/
rg/pgsql-hackers/2010-07/msg00512.php
--
Euler Taveira de Oliveira
http://www.timbira.com/
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
Hi,
Is there any reason the postmaster.pid and external_pid_file contents to be
different?
--
Euler Taveira de Oliveira
http://www.timbira.com/
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref
Magnus Hagander escreveu:
> We might, however, want to add a specific section to the
> *documentation* about building extensions on Windows.
>
+1.
--
Euler Taveira de Oliveira
http://www.timbira.com/
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make c
Itagaki Takahiro escreveu:
> I had the same problems before, and I wrote some hacks for VC++.
>
Isn't there such a code in core or am i missing something? Is it worth
supporting the VC++ standalone projects?
--
Euler Taveira de Oliveira
http://www.timbira.com/
--
Sent via pg
t return SQLSTATE but as you
point out, that part of the code deserves a refactoring to cover OP's case too.
--
Euler Taveira de Oliveira
http://www.timbira.com/
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
quot;0");
strncpy(conn->result->cmdStatus, conn->workBuffer.data,
CMDSTATUS_LEN);
conn->asyncStatus = PGASYNC_READY;
(I only patch the 'Command Complete' message here but it is necessary to patch
othe
aviors have the same goal
(in this case, NULL means success, i.e. sqlstate is not assigned) but it
doesn't match the spec.
[1] http://www.postgresql.org/docs/9.0/static/errcodes-appendix.html
--
Euler Taveira de Oliveira
http://www.timbira.com/
--
Sent via pgsql-hackers mailing
Robert Haas escreveu:
> On Fri, Aug 20, 2010 at 11:05 AM, Euler Taveira de Oliveira
> wrote:
>> Dmitriy Igrishin escreveu:
>>> /* NOT presents - NULL. Why not "0" ? */
>>> const char* sqlstate = Pg::PQresultErrorField(res, PG_DIAG_SQLSTATE);
>&g
Magnus Hagander escreveu:
> Was there any particular reason why this wasn't exposed before that
> I've missed, making this a bad addition? :-)
>
Not that I know of. Good catch. ;)
--
Euler Taveira de Oliveira
http://www.timbira.com/
--
Sent via pgsql-hackers mailing
umentation is correct but the code
is not) and should be correct because the spec enforces it.
--
Euler Taveira de Oliveira
http://www.timbira.com/
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
olds). What
I am investigating is a way to build an index with some user-defined
parameters. (We already have some infra-structure in reloptions for that but
it needs some work to support my idea). I have some half-baked patch that I'm
planning to submit to some of the CFs. Unfortunately, I
raid it is the only use case for this new option. If it is, it doesn't
deserve a new option. We can live with echo + initdb for those cases.
--
Euler Taveira de Oliveira
http://www.timbira.com/
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To ma
ed.
Besides we could patch pg_regress.c to ignore loading plpgsql language into
the database (instead of adding another parameter -- we already have too many
options).
--
Euler Taveira de Oliveira
http://www.timbira.com/
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
T
clues what does it cause and how to investigate it?
>
OProfile?
--
Euler Taveira de Oliveira
http://www.timbira.com/
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
Magnus Hagander escreveu:
> If we want to do this, I'd be inclined to say we sneak this into 9.0..
> It's small enough ;)
>
I'm afraid Robert will say a big NO. ;) I'm not against your idea; so if
nobody objects go for it *now*.
--
Euler Taveira de Oliv
Fujii Masao escreveu:
> Here is the patch which provides those three parameters as conninfo
> options. Should this patch be added into the first CommitFest for v9.1?
>
Go ahead.
--
Euler Taveira de Oliveira
http://www.timbira.com/
--
Sent via pgsql-hackers mailing list (pgsq
Marko Kreen escreveu:
> 3) Support all 3 parameters (keepidle, keepintvl, keepcnt)
> and ignore parameters not supported by OS.
>
+1. AFAIR, we already do that for the backend.
--
Euler Taveira de Oliveira
http://www.timbira.com/
--
Sent via pgsql-hackers mailing list (pgsq
Mark Mielke escreveu:
> Of course, then I'll ask for the ability to simplify specifying multiple
> databases:
>
We already support multiple users and/or databases for a single pg_hba.conf
line ...
--
Euler Taveira de Oliveira
http://www.timbira.com/
--
Sent via pgsql-hacker
_name ] | code } ...
--
Euler Taveira de Oliveira
http://www.timbira.com/
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
Takahiro Itagaki escreveu:
> Should we fix the documentation when we add the tab completion?
>
Yes, it seems consistent with other commands having optional parameters in the
middle of the command rather than at the end.
--
Euler Taveira de Oliveira
http://www.timbira.com/
--
Se
ke the %s idea. IMHO fixing pg_standby for SR is a must-fix. I'm
foreseeing a lot of users asking why pg_standby doesn't work on SR mode ...
--
Euler Taveira de Oliveira
http://www.timbira.com/
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make chan
w us the definition of m_a, temp_m_t, and related tables?
--
Euler Taveira de Oliveira
http://www.timbira.com/
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
w beforehand what are the default configure options.
Of course, parsing the configure output and greping the interested options is
a boring task but at least it is all there; but it's not a summary. :(
--
Euler Taveira de Oliveira
http://www.timbira.com/
--
Sent via pgsql-hacke
Alvaro Herrera escreveu:
> The general idea seems sensible to me. I can't comment on the
> specifics.
>
+1. A lot of other programs have this summary at the end of configure
execution. The problem is that PostgreSQL has too many options. Do we want to
list all of them?
--
Eu
pgxs gives different
> names to .so.
>
What the problem with that? If it set up the right name in sql file that's OK.
IMHO, you're trying to complicate a simple process. If you messed up your
installation you can always do:
$ cd mymodule
$ USE_PGXS=1 make uninstall
--
Euler Tav
27;t need root; I mean, you can always set absolute path or even the
dynamic_library_path [2] parameter.
[1] http://www.postgresql.org/docs/8.4/static/xfunc-c.html#DFUNC
[2]
http://www.postgresql.org/docs/8.4/static/runtime-config-client.html#RUNTIME-CONFIG-CLIENT-OTHER
--
Euler Taveira de Oliveira
htt
APIs. A reasonable target is 10.0. ;)
--
Euler Taveira de Oliveira
http://www.timbira.com/
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
already have; besides, it will be intuitive
for users.
[1] http://archives.postgresql.org/pgsql-hackers/2010-01/msg01317.php
--
Euler Taveira de Oliveira
http://www.timbira.com/
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
problem of your patch but it needs to be fixed is
that resetting functions remove the line from pg_stat_user_functions; that a
different behavior from other pg_stat_user_* functions.
--
Euler Taveira de Oliveira
http://www.timbira.com/
--
Sent via pgsql-hackers mailing list (pgsql-hackers
lp command. If we
do that, we'll see requests like "why don't you add _my-favorite-db-here_ help
too?". So, -1.
--
Euler Taveira de Oliveira
http://www.timbira.com/
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
Dimitri Fontaine escreveu:
> It should be possible to be in contrib and installed by default, even
>
And it could be uninstall too. Let's not do it for core functionalities.
--
Euler Taveira de Oliveira
http://www.timbira.com/
--
Sent via pgsql-hackers mailing list (pg
1 - 100 of 289 matches
Mail list logo
