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
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
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
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/
--
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
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
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
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
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
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
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
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
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
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
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
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
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,
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
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
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
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
_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
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
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
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
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
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 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
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.
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
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
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
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
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
gth of the
work queue, or something like that?
Yes, there is. As I said, it is an expensive and approximate measure. I'm not
saying that is not the right direction, I'm arguing that a hint is better than
nothing. Right now the only way to know if it is out of workers is to query
pg_stat_
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
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,
/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
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
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'
m, no?
> This never happened earlier with postgres 9.0 Is there a known issue
> with Postgres 9.1? Or how to report this problem?
>
Test case? Query times? Query plans? Are you sure you the compile options are
the same? What about the configuration parameters? What is the exact version
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
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 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
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
bilizar this my small
> contribution.
>
This is not the right list. Just send your updated version to
[EMAIL PROTECTED] so one of the committers can apply it.
--
Euler Taveira de Oliveira
http://www.timbira.com/
---(end of broadcast)-
markup
--
Euler Taveira de Oliveira
http://www.timbira.com/
---(end of broadcast)---
TIP 7: You can help support the PostgreSQL project by donating at
http://www.postgresql.org/about/donate
.
Will it be possible to disable stemming or stopwords removal? I'm asking
this 'cause sometimes stemming doesn't lead to good results and/or
stopwords are relevant. Maybe it could be an GUC variables
('enable_stemming' and 'enable_stopwords').
--
Euler Tavei
is in english or japanese. So you have two options:
(a) disable stemming (b) leave the language set to 'japanese' and see if
it plays well.
--
Euler Taveira de Oliveira
http://www.timbira.com/
---(end of broadcast)---
TIP 7
What you're looking for is silent installation [1].
> 2) Start postgres when the app starts.
> 3) Stop postgres when the app stops.
pg_ctl?
> 4) Minimize the amount of postgres processes.
>
You can't. It's by design.
[1] http://pginstaller.projects.postgresql.org/silent
What you're looking for is silent installation [1].
> 2) Start postgres when the app starts.
> 3) Stop postgres when the app stops.
pg_ctl?
> 4) Minimize the amount of postgres processes.
>
You can't. It's by design.
[1] http://pginstaller.projects.postgresql.org/silent
in pthread_mutex_lock () from /lib/libc.so.6
#10 0xb7fc2d49 in ?? () from /usr/lib/libpq.so.5
#11 0x0001 in ?? ()
#12 0x in ?? ()
(gdb)
--
Euler Taveira de Oliveira
http://www.timbira.com/
---(end of broadcast)---
TIP 7: You can
d it. :( I'll take a look and this.
[1] http://archives.postgresql.org/pgsql-hackers/2006-11/msg00523.php
--
Euler Taveira de Oliveira
http://www.timbira.com/
---(end of broadcast)---
TIP 7: You can help support the PostgreSQL project by donating a
Joshua D. Drake wrote:
> The docs since 7.3 have declared the money type deprecated.. that is an
> awful long time. Can we get some clarity on the issue?
>
IMHO it's not but it certainly need some more work on the storage
(numeric?) and locale part as already discussed.
--
Eu
de somewhere in
the ftp.postgresql.org. IMHO pgfoundry project will confuse people.
--
Euler Taveira de Oliveira
http://www.timbira.com/
---(end of broadcast)---
TIP 7: You can help support the PostgreSQL project by donating at
http:/
;t remember what locale is. I'll check it.
> This test is with 8.3-HEAD and the patch to allow UTF-8.
>
I tested with 8.2.4 and my encoding is LATIN1 IIRC. Didn't try UTF-8.
I'll give it a try when i have my dev environment.
--
Euler Taveira de Oliveira
http://www.timb
that PostgreSQL agrees with glibc (even it's the wrong
behavior). Given this assumption, i propose the attached patch (it needs
to adjust the regression tests).
Comments?
[1] http://archives.postgresql.org/pgsql-bugs/2006-09/msg00074.php
--
Euler Taveira de Oliveira
http://www.tim
uld accept the thousands_sep from glibc instead
of guessing it ("."). I'm fine with the current behavior (at least in
pt_BR) but I'm afraid we have broken some locales (those that a
presented in the lcnumeric.diff).
--
Euler Taveira de Oliveira
http://www.timbira.com
s broken too. In PostgreSQL, it's
following the en_US behavior. Comments?
[EMAIL PROTECTED]:/a/pgsql$ ./a.out C
decimal_point: "."
thousands_sep: ""
[EMAIL PROTECTED]:/a/pgsql$ ./a.out en_US
decimal_point: "."
thousands_sep: ","
[1] http:/
jMartinez wrote:
Would it be possible to add an option to the pg 8.3 Windows installer to
separate the pg_log and pg_xlog folders from tha data one?
Both options already exist in 8.3; pg_log can be set in postgresql.conf
('log_directory') and pg_xlog can be set at initdb time.
we agree we need to
do a fine tune to benefit from this feature, we will need to deprecate
'enable_sync_seqscans' and invent another one (sync_seqscans_threshold).
Looking at this perpective, IMHO we should go with the number (0.25)
instead of the boolean.
--
Euler
ay the
patch was proposed and suggested changes. Let's see if the Takahiro-san did
everything that was suggested.
--
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
nly accessible to superusers?
>
If the utility command hook patch is approved, it will be possible to track
commands rather than DML ones. In that case, it would be trivial to do some
extension that covers your audit concerns.
[1] https://commitfest.postgresql.org/action/patch_view?id=196
--
Ron Mayer escreveu:
> While there's no great way to make this a contrib module today,
> would it make sense to add such hooks for an eventual module system?
>
I don't think so. It's easier to code a converter tool.
--
Euler Taveira de Oliveira
http://www.timbira.
need this information in all nodes (even
in those nodes that don't read or write). It would be less verbose but it
could complicate some parser's life. Of course, if we suppress this
information, we need to include it on the top node even if we don't read or
write in it.
I didn&
tmaster.c:3366
#16 0x082a69ab in BackendStartup (port=0x85d4860) at
/a/pgsql/dev/postgresql/src/backend/postmaster/postmaster.c:3073
#17 0x082a3d1c in ServerLoop () at
/a/pgsql/dev/postgresql/src/backend/postmaster/postmaster.c:1399
#18 0x082a344d in PostmasterMain (argc=3, argv=0x85b33e0) at
/a/pg
Alvaro Herrera escreveu:
> Fortunately the author of auto_explain can now commit the fix by himself ...
> Kudos, BTW :-)
>
Congratulations!
--
Euler Taveira de Oliveira
http://www.timbira.com/
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make change
reads, and Blocks of temp reads.
>
But the latter is more clear than the former.
> I cannot understand what you mean -- should I suppress the lines when they
> have all-zero values?
>
There are nodes that don't read or write blocks. If we go this way, we need to
document
t and materialized plans,
respectively. The number of blocks of an upper-level node includes the blocks
of all its child nodes. It should be used with ANALYZE
parameter. This parameter defaults to FALSE.
If there is no more objections, I'll flag the patch 'ready for committer
uot;Filter:").
>
If people object to it, we can always change it later.
> IMHO, we could remove those options completely because we can use
> EXPLAIN BUFFERS and DTrace probes instead of them.
>
+1. But we need to propose some replacement options.
--
Euler Taveira de Oliveira
s using , or ; in
any output node. The suggested output is intuitive and similar to other nodes
patterns.
[1] http://archives.postgresql.org/pgsql-hackers/2009-10/msg00718.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
nes, no one would
> even be suggesting parentheses.
>
That's the point. I'm afraid 3 new lines per node is too verbose.
--
Euler Taveira de Oliveira
http://www.timbira.com/
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscr
more correct and idiomatic. Slightly revised patch attached for
> your consideration. The output format looks really nice (thanks for
> bearing with me), and the functionality is great.
>
Please, document that zero values are omitted in the text format. It seems
intuitive but could be surprise becau
approach is http://explain.depesz.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
David E. Wheeler escreveu:
> A list of such words, to be included in the Changes file, would be most
> useful I expect.
>
As we're on this topic, could we expose keywords in a system view like say
pg_keywords?
--
Euler Taveira de Oliveira
http://www.timbira.com/
--
7;t you use vpath builds when
using your favorite SCM? That way, we don't have trouble with auto-generated
files while getting your patch.
--
Euler Taveira de Oliveira
http://www.timbira.com/
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to y
Greg Smith escreveu:
> pg_stat_reset( which text )
> which := 'buffers' | 'checkpoints' | 'tables' | 'functions' | ...
>
What about adding 'all' too? Or the idea is resetting all global counters when
we call pg_stat_reset() (wi
ion
log_after_rotation_command = 'gzip %f && mv %p.gz /a/mylogs'
Depending on the comments, I will clean up the patch and send it later today.
--
Euler Taveira de Oliveira
http://www.timbira.com/
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql
and %f are relative log path and log filename, respectively.
--
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
s improve it.
> We have "Logging Brainstorm" topic in out wiki. It might help you.
> http://wiki.postgresql.org/wiki/Logging_Brainstorm
>
Interesting. Don't know about that. Why some of those ideas aren't in our TODO?
--
Euler Taveira de Oliveira
http://www.timbira
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
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
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
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
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
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
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
://archives.postgresql.org/pgsql-hackers/2008-08/msg00176.php
--
Euler Taveira de Oliveira
http://www.timbira.com/
Index: doc/src/sgml/ref/initdb.sgml
===
RCS file: /a/pgsql/dev/anoncvs/pgsql/doc/src/sgml/ref/initdb.sgml,v
Robert Treat escreveu:
On Saturday 09 August 2008 21:31:28 Euler Taveira de Oliveira wrote:
Hi,
After the Magnus patch [1], that make it possible store statistics files
at another (RAM-based) disk, I was thinking that would be useful to add
an option at initdb time to do the symlink as we
ment_information
[2] http://wiki.postgresql.org/wiki/Todo
--
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
we could introduce another
> column that would reflect the role name.
>
Why not add another column: current_usename? I would object if we've
intended to change the view semantics.
[1] http://www.postgresql.org/docs/8.3/static/sql-set-role.html
[2]
http://www.postgresql.org/docs/8.3/static/
pgstat per table or database
and (ii) make the pgstat time tunable per table or database. You can use
the reloptions column to store these info. These workarounds are much
simpler than that you proposed and they're almost for free.
--
Euler Taveira de Oliveira
http://www.timbira.com/
--
ing
> successfully.
>
There is something wrong with your setup. You don't post what steps you
followed. Are you sure there is nothing at the logs?
--
Euler Taveira de Oliveira
http://www.timbira.com/
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgr
tions 'cause
we need a different struct to store reloptions. Suggestions?
I'm attaching the WIP patch so you can comment on it. I want to continue
working on it but I'm afraid you already did more than I do (in this
case, let me know for not duplicating efforts).
--
Euler Taveira de Oli
ould be used to both -- fillfactor) and to add it in the
validation 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
a <[EMAIL PROTECTED]> wrote:
>
>> Euler Taveira de Oliveira wrote:
>>> What did I already do? I refactored reloptions.c to support multiple
>>> options. I tried to follow up the same way GUC do (of course, it is much
>>> simpler). I'm thinking about removin
Euler Taveira de Oliveira escreveu:
> [Sorry for the delay. I'm preparing the final patch and in a day or so
> I'll post it.]
>
Here is the patch that replace pg_autovaccum catalog with reloptions. I
refactored the reloptions.c to support multiple parameters and made the
act
ion.
>
I already tried that and don't use because of portability issues. But I
don't thing 3 (maybe 4 -- when we have string types in it) loops in
sequence are so ugly. IMHO, we can live with that.
--
Euler Taveira de Oliveira
http://www.timbira.com/
--
Sent via pgsql-hacke
;t rip out the StdRdOptions just to maitain the
RelationGetFillFactor() and others like a macro. Honestly, I don't like
to bring RelationGet*() to reloptions.c but we can always refactor that
before committing it.
Alvaro, let me know if you want me to send another patch; or will you do
ut if you think it's important to
exercise that code path, I will elaborate some tests.
[1] http://archives.postgresql.org/pgsql-hackers/2008-11/msg01494.php
[2] http://archives.postgresql.org/pgsql-hackers/2008-11/msg01500.php
--
Euler Taveira de Oliveira
http://www.timbira.com/
reloptv2.d
201 - 300 of 441 matches
Mail list logo
