=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
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 Taveira de Oliveira
).
--
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
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
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 Oliveira
http://www.timbira.com/
--
Sent via
Brendan Jurd escreveu:
2009/7/31 Euler Taveira de Oliveira eu...@timbira.com:
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.23E+02
I don't think neglecting to represent a valid
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.com/
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes
for a
committer.
[1]
http://download.oracle.com/docs/cd/B19306_01/server.102/b14200/sql_elements001.htm#sthref80
--
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
' 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 above in regression tests too.
--
Euler Taveira de Oliveira
http://www.timbira.com/
--
Sent via
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-hackers@postgresql.org)
To make
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
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@postgresql.org)
To make changes to your
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://www.timbira.com
? It is short and simple.
Child tables: daughter,
daughter2,
daughter3,
plop.daughter4
Has OIDs: no
Since the child list can be rather long, it's probably better to put
everything else first, e.g. the Has OIDs line.
+1. Don't forget Options.
--
Euler
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
have 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
/Objects/dictobject.c?revision=70550view=markup
[3] http://bugs.python.org/issue5627
--
Euler Taveira de Oliveira
http://www.timbira.com/
Index: plpython.c
===
RCS file: /a/pgsql/dev/anoncvs/pgsql/src/pl/plpython/plpython.c,v
retrieving
Alvaro Herrera escreveu:
Euler Taveira de Oliveira wrote:
Tom Lane escreveu:
Alvaro Herrera alvhe...@commandprompt.com writes:
... However, on HEAD this is crashing for me, and it's right when plpython
loads. Backtrace below.
Does plpython pass its regression tests for you (I'd suppose
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 changes to your
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 Taveira de Oliveira
http://www.timbira.com/
--
Sent via pgsql-hackers
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 mailing list
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/
--
Sent
#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
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/
--
Sent via pgsql
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 user has 7.4 and install 8.3 then the package
will replace
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:
http://www.postgresql.org/mailpref/pgsql-hackers
* 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
-{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
and relopt defaults are different
(autovacuum_cost_delay and autovacuum_cost_limit). Is there any reason for not
using -1?
(iv) Maybe we should document that pg_dump will only dump reloptions like
toast.foo iff the relation has an associated TOAST table. This seems obvious
but ...
--
Euler
.
--
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 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.org)
To make changes to your subscription:
http
+--+---+--+---
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_strings = off;
SET check_function_bodies = false;
SET
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 *validnsps[] = { toast };
Surely, you forgot to add
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 it, because it
works, but it still allows this:
IMHO it's
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 subscription:
http
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
...
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 code.
--
Euler Taveira de Oliveira
http
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
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 Taveira de Oliveira
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 subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
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 (pgsql-hackers@postgresql.org)
To make changes
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 right now). I proposed writing these history
.
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?).
--
Euler Taveira de Oliveira
http://www.timbira.com/
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org
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
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 it still allows this:
IMHO it's the appropriate place
.
--
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
/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
)
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
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 subscription:
http://www.postgresql.org/mailpref
ITAGAKI Takahiro escreveu:
- A new GUC variable 'explain_analyze_format' is added.
I'm afraid that this variable name doesn't tell what it means. What about
'explain_analyze_stats_format' or even 'explain_stats_format'?
--
Euler Taveira de Oliveira
http://www.timbira.com/
--
Sent via
benefit
from this feature because (i) autovacuum won't often trigger this table or
(ii) you disabled the autovacuum on that table.
Perhaps a table-level option to scan the whole table instead of
estimating would be appropriate?
ANALYZE FULL foo ?
--
Euler Taveira de Oliveira
http
Tom Lane escreveu:
Euler Taveira de Oliveira [EMAIL PROTECTED] writes:
I saw a report at .br mailing list [1] complaining about the message's title.
I do not try to investigate it. Am I missing something?
euler=# select attname from pg_attribute where attnum 0 and attnum
ALL(select
it to me? Thank you
It's only a category information. Take a look at (almost at the end of) gram.y
to understand what each category is.
--
Euler Taveira de Oliveira
http://www.timbira.com/
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your
)
[1]
http://listas.postgresql.org.br/pipermail/pgbr-geral/2008-December/013277.html
--
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
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.diff.gz
Description: GNU Zip compressed data
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-hackers mailing list (pgsql-hackers
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
it? I have some small corrections too.
--
Euler Taveira de Oliveira
http://www.timbira.com
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
action of adding a new
(getRelOptions()?) to extract the
reloption (autovacuum) parameters because we need to transform
pg_autovacuum catalog table in a view to maintain backward compatibility.
--
Euler Taveira de Oliveira
http://www.timbira.com/
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org
) 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
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 Oliveira
http://www.timbira.com/
Index
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/
--
Sent via pgsql-hackers
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@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref
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/sql-set-session-authorization.html
--
Euler Taveira de Oliveira
http://www.timbira.com/
--
Sent via pgsql-hackers
://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
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
://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
tables are
processed by autovac.
FYI, I have a WIP patch to remove pg_autovacuum in favor of reloptions.
And based on your proposal, it'll be needed to add reloptions to toast
tables too. IMO, we should keep that code as simple as possible.
--
Euler Taveira de Oliveira
http://www.timbira.com
of
adding such an option.
--
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
Greg Sabino Mullane wrote:
there another way around this problem that can be somewhat
automated?
I don't think so. This is a particular case. So my advice is to hack
test_config_settings() and add your custom values to trial_conns[] and
trial_bufs[].
--
Euler Taveira de Oliveira
http
Bernd Helmle wrote:
segment_size: Reports heap segment size
wal_segment_size: Reports wal segment size
block_size: Available yet
wal_block_size: wal block size
+1. We already have block_size in GUC.
--
Euler Taveira de Oliveira
http://www.timbira.com/
--
Sent via pgsql-hackers mailing
support
can be achieved by using the locale stuff. Comments?
I don't understand what you mean here.
I mean that you need to put locale.h and setlocale(LC_MESSAGES, ) at
.pgc so you get localized messages from ecpg program.
--
Euler Taveira de Oliveira
http://www.timbira.com/
--
Sent via
to change for awhile.
Do we need to work around this?
BTW, I sent an only-for-test pt-br translation within the patch. Maybe
we could commit it just to have one language there.
--
Euler Taveira de Oliveira
http://www.timbira.com/
--
Sent via pgsql-hackers mailing list (pgsql-hackers
Martijn van Oosterhout wrote:
This will close the file *only* if yyin is NULL, which probably isn't
what is meant.
Ops... you're right. :-)
--
Euler Taveira de Oliveira
http://www.timbira.com/
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your
for those messages. Suggestions?
--
Euler Taveira de Oliveira
http://www.timbira.com/
l10necpg2.tgz
Description: application/compressed-tar
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql
Euler Taveira de Oliveira wrote:
This is a second try.
I forgot to say that this patch doesn't include nls support to ecpg
files automagically. If you guys think that it's is a Good Thing to do,
we need to hack the preproc.y to hardcode the locale stuff; if you
decide that it isn't
() at y.tab.c:20322
#6 0x0806ca35 in main (argc=2, argv=0xbff0ea94) at
/a/pgsql/dev/pgsql/src/interfaces/ecpg/preproc/ecpg.c:462
(gdb) print yyin
$1 = (FILE *) 0x0
--
Euler Taveira de Oliveira
http://www.timbira.com/
*** ./src/interfaces/ecpg/preproc/preproc.y.orig 2008-05-11 01:28
Alvaro Herrera wrote:
Huh, isn't the test backwards?
In which way? I use a simple one but whatever test that uses 'exec sql
include foo' and foo.h doesn't exist, it will crash.
--
Euler Taveira de Oliveira
http://www.timbira.com/
--
Sent via pgsql-hackers mailing list (pgsql-hackers
,
questionmarks=0, name=0x8048819 f, variable=0xbfccc72c select * from
foo limit 1,2)
at /a/pgsql/dev/pgsql/src/interfaces/ecpg/ecpglib/prepare.c:128
#2 0x0804865d in main ()
--
Euler Taveira de Oliveira
http://www.timbira.com/
Index: src/interfaces/ecpg/ecpglib/prepare.c
Andrew Dunstan wrote:
Committed with slight editorializing. Statement timeout was only
introduced in 7.3, whereas pg_dump can dump from much older versions of
Postgres.
You forget a ; in this committ [1].
[1] http://archives.postgresql.org/pgsql-committers/2008-05/msg00028.php
--
Euler
agree with Tom that it's is a
in-progress-work. I'll send another revision of the first patch later.
--
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
that an overhaul of ecpg_log,
ecpg_raise, mmerror and base_yyerror functions is necessary. I'll give
it a try later.
[1] http://www.postgresql.org/docs/8.3/static/nls-programmer.html
--
Euler Taveira de Oliveira
http://www.timbira.com/
l10necpg.tgz
Description: application/compressed-tar
/* ?
--
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
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 Taveira de Oliveira
http://www.timbira.com
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.
--
Euler
(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/
---(end of broadcast)---
TIP 3: Have you checked our extensive FAQ
]:/a/pgsql$ ./a.out C
decimal_point: .
thousands_sep:
[EMAIL PROTECTED]:/a/pgsql$ ./a.out en_US
decimal_point: .
thousands_sep: ,
[1] http://timbira.com/tmp/lcn3.sql
[2] http://timbira.com/tmp/lcnumeric.diff
--
Euler Taveira de Oliveira
http://www.timbira.com/
---(end
). 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.timbira.com/
#include stdio.h
#include locale.h
int main(int argc, char *argv
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.timbira.com/
---(end
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://www.postgresql.org
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.
--
Euler Taveira de
://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 at
http://www.postgresql.org/about/donate
() 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 help support the PostgreSQL
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.html
--
Euler Taveira de Oliveira
http
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.html
--
Euler Taveira de Oliveira
http
results and/or
stopwords are relevant. Maybe it could be an GUC variables
('enable_stemming' and 'enable_stopwords').
--
Euler Taveira de Oliveira
http://www.timbira.com/
---(end of broadcast)---
TIP 2: Don't 'kill -9' the postmaster
:
(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: You can help support the PostgreSQL project by donating
--
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
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)---
TIP 3: Have you checked
301 - 400 of 437 matches
Mail list logo