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
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
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
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
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
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/
--
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
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
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
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
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
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
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
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
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
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&
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.
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
--
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
adding some code to capture VACUUM and
ANALYZE commands called inside autovacuum.
--
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,
I noticed that some example functions don't contain the magic block and that
leads to error while loading those examples in 8.2 or later.
Attached is a patch that adds it. I also add some missing header file. Don't
have a strong opinion about backpatching it or not.
--
Euler
Wojciech Knapik escreveu:
>
> Euler Taveira de Oliveira wrote:
>
>>> PS. This issue is not related to the loading time of dictionaries, or
>>> calls to ts_headline for results that won't be displayed.
>>
>> So what? Could you post the profiling
Robert Haas escreveu:
> On Tue, Nov 17, 2009 at 6:39 PM, Euler Taveira de Oliveira
> wrote:
>> Alex Hunsaker escreveu:
>>> BTW anyone know how to escape < and > for google?
>>>
>> You can escape < and > using < and >, respectively.
>
>
Wojciech Knapik escreveu:
> PS. This issue is not related to the loading time of dictionaries, or
> calls to ts_headline for results that won't be displayed.
>
So what? Could you post the profiling of that query?
--
Euler Taveira de Oliveira
http://www.timbira.com/
--
Alex Hunsaker escreveu:
> BTW anyone know how to escape < and > for google?
>
You can escape < and > using < and >, respectively.
--
Euler Taveira de Oliveira
http://www.timbira.com/
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
Simon Riggs escreveu:
> So, I
> propose that we simply ignore patches from developers until they have
> done sufficient review to be allowed to develop again.
>
Is it really impolite for a first-contributor, no?
--
Euler Taveira de Oliveira
http://www.timbira.com/
--
Se
month. I don't know if it
would be as effective as it has been done but it will take that weight off our
CM's shoulders.
--
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
ic walreceiver but
with some aditional features such as wal filtering then (s)he is free to do it
because we provide entry points in the API.
BTW, are you going to submit another WIP patch for next commitfest?
--
Euler Taveira de Oliveira
http://www.timbira.com/
--
Sent via pgsql-hacker
to do it.
>
+1. That's what I have in mind 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
o:
"/a/pgsql/src/backend/commands/trigger.c", Linha: 3893)
Why don't you use the syntax (DEFERRABLE and INITIALLY DEFERRED)? That will do
the Right Thing (TM).
BTW, is it worth preventing such a crash putting an elog message in trigger.c?
--
Euler Taveira de Oliveira
http://www.ti
ave it alone for now, unless it's few lines of 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
ld we call
pgstat_reset_counters() in a new-function (assign_track_counts(?) that will be
in assign_hook for guc 'track_counts')?
--
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:
plication
> name (my guess is 'no').
> b) Updated the apps to use PQconnectdb
> c) Something else?
>
My prefered option is (b). But it should be a separate patch.
--
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
ntrols in which he actually add
> syntax for row level permission in that catalog, something we don't
> have in any other place yet) is really a system catalog?
>
IMHO it's hibrid (catalog and regular table). That' why people proposed the
SET TABLESPACE and ACL.
--
think. Am I missing something?
>
No. BTW, I have an unpublished version here that I didn't commit because I
need to clean it up. :(
--
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
1] http://archives.postgresql.org/pgsql-hackers/2004-06/msg00835.php
[2] http://listas.postgresql.org.br/pipermail/pgbr-geral/2009-March/014374.html
--
Euler Taveira de Oliveira
http://www.timbira.com/
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes
rmission.
IMHO the owner should be preserved. In my mind, REPLACE is for changing the
content and not the properties (name, owner, etc).
--
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
opy from the server.
--
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
de like cracklib, it probably is going to have to be on
>> pgfoundry not in contrib.
>
> Why is that? we have plenty of other things in contrib that rely on
> external code, for example the uuid, xml or ssl stuff.
>
Because cracklib is GPL'ed.
--
Euler Taveira de Oliveira
're walking up the tree. Also, you need to decide what to do when
you have more than one node per level. :( How do you deal with priority in
this case?
--
Euler Taveira de Oliveira
http://www.timbira.com/
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make c
Robert Haas escreveu:
> On Thu, Oct 1, 2009 at 11:47 AM, Tom Lane wrote:
>> Euler Taveira de Oliveira writes:
>>> Tom Lane escreveu:
>>>> daveg writes:
>>>>> I'd like to propose adding a new GUC to limit the amount of memory a
>>>>
Tom Lane escreveu:
> daveg writes:
>> I'd like to propose adding a new GUC to limit the amount of memory a backend
>> can allocate for its own use.
>
> Use ulimit.
>
What about plataforms (Windows) that don't have ulimit?
--
Euler Taveira de Oliveira
htt
rt files, hash files, and
> materialized executor plan. Local buffer statistics for temp tables are
> not included here but merged with shared buffer statistics. Are there
> any better way to group them?
>
Are you sure? Looking at ReadBuffer_common() function I see an 'if
(isLoc
ht place for these counters. Maybe we should
put it in buf_init.c. Ideas?
> boolcosts; /* print costs */
> + boolbuffer; /* print buffer stats */
Rename it to "buffers".
> + /* Buffer usage */
> + long
3381 MemoryContextReset
992.3147 MemoryContextAlloc
481.1223 SPI_pop
41 0.9586 SPI_push
--
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
.1087 list_head
941.0635 ResourceOwnerEnlargePlanCacheRefs
901.0182 ResourceOwnerRememberPlanCacheRef
440.4978 SPI_push
390.4412 SPI_pop
Any ideas?
[1]
http://listas.postgresql.org.br/pipermail/pgbr-geral/2009-September/017427.html
--
Euler Taveira de Oliveira
http://www
he same (i didn't
remember any complaints about that but ...).
So +1 for this 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
Tom Lane escreveu:
> Euler Taveira de Oliveira writes:
>> Peter Eisentraut escreveu:
>>> Possibly, but there aren't going to be any new translations within the
>>> next two days. We may want to reconsider this for the next alpha.
>>>
>> IMHO,
it's too much work for an alpha cycle. Why not encourage it _only_ after
the last commitfest?
--
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
ng 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
ttps://commitfest.postgresql.org/action/commitfest_view?id=3
--
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
used if we have 2 or 3 exponent digits (that is the same behavior
Oracle has).
--
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
Tom Lane escreveu:
> The real bottom line for to_char issues is almost always that we should
> do what Oracle does. Has anyone checked this behavior on Oracle?
>
That was my point too. See [1].
[1] http://archives.postgresql.org/pgsql-hackers/2009-07/msg01870.php
--
Euler T
Brendan Jurd escreveu:
> 2009/7/31 Euler Taveira de Oliveira :
>> Brendan Jurd escreveu:
>>> Limiting to two exponent digits also has the nice property that the
>>> output always matches the length of the format pattern:
>>>
>>> 9.99
>>> 1
e test is not in the switch because it
> doesn't belong there.
>
It was just a suggestion. If you think it is self-explanatory, so it is. But I
(as the first time reading that piece of code) take some time to figure out
why that test is outside the switch.
--
Euler Taveira de Olivei
erty".
What does the length of format pattern have to do with output format?
--
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
7;case' clause to test if was
previously used (that was one suggestion) but I said if you don't want to go
that way, add a comment explaining why you're using that 'if' above the
'switch' and not inside it.
--
Euler Taveira de Oliveira
http://www.timbira
t + 6)
+ {
+ numstr = (char *) palloc(Num.pre + Num.post + 7);
+ fill_str(numstr, '#', Num.pre + Num.post + 6);
+ *(numstr + Num.pre) = '.';
+ }
I can't see more problems in your patch. When you fix it, it'll be ready for
#x27;)
---
1.2E+03
1 rows selected
The '9.999' format error message is misleading.
euler=# select to_char(123, '9.999');
ERRO: cannot use "" twice
You could include an example in manual too. You could add the two failing
cases
Merlin Moncure escreveu:
> Isn't it possible though to write and/or review the documentation
> patch without building it?
>
cd pgsql/doc/src/sgml && gmake check
--
Euler Taveira de Oliveira
http://www.timbira.com/
--
Sent via pgsql-hackers mailing list (pgsql-hack
t do? If we can't fix it now,
at least we add it to 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
ws? I would confuse
users and programs that parses the EXPLAIN output. However, I wouldn't object
to add ntuples to an extended explain output (as discussed in the other thread).
--
Euler Taveira de Oliveira
http://www.timbira.com/
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postg
Hi,
While translating some pg_dump messages I noticed that some messages could be
part of plural form. I attached a patch that catches those remaining messages.
--
Euler Taveira de Oliveira
http://www.timbira.com/
Index: src/bin/pg_dump/pg_dump.c
Cristina M escreveu:
> - for table t2(l_orderkey int, l_partkey int, l_quantiy, l_tax,
> l_extendedprice, l_discount) I got an error of 42 %.
>
I suspect you have NULLs in your table; they're stored as bitmaps, so they use
little space.
--
Euler Taveira de Oliveira
http://w
ng, it's probably better to put
> everything else first, e.g. the "Has OIDs" line.
>
+1. Don't forget "Options".
--
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
Fujii Masao escreveu:
Is it worth making the patch which creates stats_temp_directory
if not present?
+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
ve an different
syntax and separate section in docs) and are not less special than aggregate
functions. So +1 to add \dw for them.
--
Euler Taveira de Oliveira
http://www.timbira.com/
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
Abhijit Menon-Sen escreveu:
> That this family of functions did not exist earlier was merely an
> oversight.
>
Added to next commitfest. Thanks!
--
Euler Taveira de Oliveira
http://www.timbira.com/
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make c
Alvaro Herrera escreveu:
> Euler Taveira de Oliveira wrote:
>> Tom Lane escreveu:
>>> Alvaro Herrera writes:
>>>> ... However, on HEAD this is crashing for me, and it's right when plpython
>>>> loads. Backtrace below.
>>> Does plp
stringobject.c?revision=70682&view=markup
[2]
http://svn.python.org/view/python/trunk/Objects/dictobject.c?revision=70550&view=markup
[3] http://bugs.python.org/issue5627
--
Euler Taveira de Oliveira
http://www.timbira.com/
Index: plpython.c
===
guish between
system, user, or both. Also, I don't think people frequently change the search
class (system, user, or both) so I don't buy the argument that it is more
easier to type another letter each time than typing a '\set FOO bar' once per
dozens of commands.
--
Euler T
Michael Toews escreveu:
> This feature request is for PG to support -infinity and infinity for date
> types.
>
This was done for 8.4. Look at TODO [1].
[1] http://wiki.postgresql.org/wiki/Todo
--
Euler Taveira de Oliveira
http://www.timbira.com/
--
Sent via pgsql-hackers mai
Zichen Xu escreveu:
> Also, I have modified the funscopy.c and every related place where the
^
This file doesn't exist on PostgreSQL source code.
Out of curiosity, what another cost metric is for?
--
Euler Taveira de Oliveira
http://www.timbira.com/
c/routine-vacuuming.html#AUTOVACUUM
--
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
Alvaro Herrera escreveu:
> Euler Taveira de Oliveira wrote:
>> Peter Eisentraut escreveu:
>>> If no such list exists yet, perhaps we can complete the above one, document
>>> it, and pass it on to the packagers.
>>>
>> Are you suggesting that if an use
that help them
(psql --version ?) and we will have extra effort to maintain the compatibility
version list at each binary.
IMHO, we shouldn't advise packagers to do it and instead put some efforts in
the in-place-upgrade project.
--
Euler Taveira de Oliveira
http://www.timbira.com/
--
eed to hardcode the namespace notion at psql code.
[1] http://archives.postgresql.org/pgsql-hackers/2009-02/msg00042.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:
h
#x27; is not. I don't like terminology changes too but in this
case it sounds strange calling autovacuum_* as storage parameters.
--
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
ast.foo iff the relation has an associated TOAST table. This seems obvious
but ...
--
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
and 'reloption' (?) means only process those tables
that have reloption autovacuum_enabled=true. The con is that we couldn't
implement a per-{schema,database} switch for autovacuum. So I prefer the first
one.
--
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
>
Ah, idea withdrawn. But we should at least document this behavior.
--
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
vise DBA to run
pg_upgrade two times. I prefer a solution where we know beforehand the size
per tuple so when we're rewriting we could use this information to upgrade.
--
Euler Taveira de Oliveira
http://www.timbira.com/
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.
Euler Taveira de Oliveira escreveu:
[Forgot the first patch...]
> Alvaro Herrera escreveu:
>> New patch attached, with pg_dump support (thanks to Tom for the SQL
>> heads-up).
>>
> Great! We're close. Just two minor gripes:
>
> + char *validnsp
Tipo | Modificadores | Storage | Descrição
+--+---+--+---
a | text | | extended |
Têm OIDs: não
--
Euler Taveira de Oliveira
http://www.timbira.com/
--
-- PostgreSQL database dump
--
SET statement_timeout = 0;
SET client_encoding = 'UTF8';
SET standard_conforming
Alvaro Herrera escreveu:
> Alvaro Herrera wrote:
>> Euler Taveira de Oliveira wrote:
>>> Alvaro Herrera escreveu:
>>>> I wasn't sure of the best place to add a check. I have added it to
>>>> transformRelOptions; I am not entirely comfortable with
his properly now by just revoking
> permissions on a specific column.
>
+1. What about pg_authid, pg_roles, pg_user, and pg_shadow?
--
Euler Taveira de Oliveira
http://www.timbira.com/
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your
tool usability (you can always start/stop statement collection
at runtime).
--
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
question is what you were doing to pg_namespace...
>
> The bug was dereferencing uninitialized pointer, and postgres dumps core
> immediately. And patch does nothing with namespace.
>
Could you post a backtrace or a test case? Maybe it is worth adding an assert
or test at some point in the
Bryce Nesbitt escreveu:
> Here's a revision (thanks Robert Treat for the spelling corrextion).
> If there are no other objections, how do I nominate it for consideration?
>
Added to next commit fest [1].
[1] http://wiki.postgresql.org/wiki/CommitFest_2009-First
--
Euler Tavei
as that different
kinds have different min/max values (see fillfactor for an example).
--
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
Alvaro Herrera escreveu:
> Euler Taveira de Oliveira escribió:
>> Alvaro Herrera escreveu:
>>> This could be solved if the workers kept the whole history of tables
>>> that they have vacuumed. Currently we keep only a single table (the one
>>> being vacuumed r
ourse some lock mechanism needs to exist to
guarantee that we don't write at the same time. The size of this linked list
would be scale by a startup-time-guc or a reasonable fixed value.
--
Euler Taveira de Oliveira
http://www.timbira.com/
--
Sent via pgsql-hackers mailing list (p
feature in core that is not SQL
standard (aka SQL/XML) but maybe it could be an external module.
[1] http://wiki.postgresql.org/wiki/XML_Todo
--
Euler Taveira de Oliveira
http://www.timbira.com/
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your s
seq_page_cost/random_page_cost. But I'm leaning towards a simple
>> hard-coded value for now.
>
> Yes, sounds good. Can we stick to multiples of 2 as the OS readahead
> does IIRC? So either 16 or 32. I'd go 32.
>
Agreed. And do it a constant (ALL_VISIBLE_VM_THRESHOLD?)
to be found on the
> root source directory. It seems the most natural way to do this. Am I
> alone in this?
>
No, I do it 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
Alvaro Herrera escreveu:
> Euler Taveira de Oliveira wrote:
>> Alvaro Herrera escreveu:
>>> I wasn't sure of the best place to add a check. I have added it to
>>> transformRelOptions; I am not entirely comfortable with it, because it
>>> works, but i
et (toast.fillfactor = 20);
> ALTER INDEX
>
Maybe you need to add relopt_kind test in your 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
s.
[1] http://archives.postgresql.org/pgsql-hackers/2008-12/msg00292.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
llow-on commits)
>
> What still remains to be done for 8.4?
>
autovacuum part?
--
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
it with good
documentation). What about xxx_toast reloptions? The con is that we need to
add 2 reloptions if the new reloption is table-related.
--
Euler Taveira de Oliveira
http://www.timbira.com/
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your
101 - 200 of 289 matches
Mail list logo
