by external
variables, like LC_TIME.
As it is though, I'm not sure why you're using to_char here, surely
extract or date_truc would be more appropriate?
Have a nice day,
--
Martijn van Oosterhout kleptog@svana.org http://svana.org/kleptog/
From each according to his ability. To each according to his
against random data corruption, in normal
operation it is never read. If we want to detect random corruption,
we'd need checksum everywhere, yes. But that's not the goal here.
Have a nice day,
--
Martijn van Oosterhout kleptog@svana.org http://svana.org/kleptog/
From each according to his
, but getting access to it is not
easy. Using a table may to easier, but you'll need to provide more
details if you want more help.
Have a ncie day,
--
Martijn van Oosterhout kleptog@svana.org http://svana.org/kleptog/
From each according to his ability. To each according to his ability
some solution to the join problem, since
at least the join path directly implied by the original clauses will
work.)
Sounds great...
PS. I'm glad you're doing this, because I wouldn't know where to
start... Keep up the good work!
Have a nice day,
--
Martijn van Oosterhout kleptog@svana.org
it again when needed rather
than printing a warning.
Have a nice day,
--
Martijn van Oosterhout kleptog@svana.org http://svana.org/kleptog/
From each according to his ability. To each according to his ability to
litigate.
signature.asc
Description: Digital signature
or vacuum or some other DDL command on the table that would
get confused by the disparity between the hint bits and the xlog.
Have a nice day,
--
Martijn van Oosterhout kleptog@svana.org http://svana.org/kleptog/
From each according to his ability. To each according to his ability
is to allowed the btree code to call the
operator to decide nulls first/last, that would allow you to factor
that part out at least.
Have a nice day,
--
Martijn van Oosterhout kleptog@svana.org http://svana.org/kleptog/
From each according to his ability. To each according to his ability
think you really have wonder whether NSS is a better
choice.
Have a nice day,
--
Martijn van Oosterhout kleptog@svana.org http://svana.org/kleptog/
From each according to his ability. To each according to his ability to
litigate.
signature.asc
Description: Digital signature
in a better world (TM).
We're in the bizarre situation were both Debian and the OpenSSL groups
beleive it is a problem, and postgresql does not. Quite odd.
Have a nice day,
--
Martijn van Oosterhout kleptog@svana.org http://svana.org/kleptog/
From each according to his ability. To each according
in the example code.
Have a nice day,
--
Martijn van Oosterhout kleptog@svana.org http://svana.org/kleptog/
From each according to his ability. To each according to his ability to
litigate.
signature.asc
Description: Digital signature
is a
useless extra step in my case).
Have a nice day,
--
Martijn van Oosterhout kleptog@svana.org http://svana.org/kleptog/
From each according to his ability. To each according to his ability to
litigate.
signature.asc
Description: Digital signature
notice.
Have a nice day,
--
Martijn van Oosterhout kleptog@svana.org http://svana.org/kleptog/
From each according to his ability. To each according to his ability to
litigate.
signature.asc
Description: Digital signature
I worked on that project.
Because there is a very large, very meaningful difference.
Have a nice day,
--
Martijn van Oosterhout kleptog@svana.org http://svana.org/kleptog/
From each according to his ability. To each according to his ability to
litigate.
signature.asc
Description
,
--
Martijn van Oosterhout kleptog@svana.org http://svana.org/kleptog/
From each according to his ability. To each according to his ability to
litigate.
signature.asc
Description: Digital signature
already been
written. So the work has already been done...
Have a nice day,
--
Martijn van Oosterhout kleptog@svana.org http://svana.org/kleptog/
From each according to his ability. To each according to his ability to
litigate.
signature.asc
Description: Digital signature
to this effect uplist]
As someone looking from the outside:
fsync only works on one file, so presumably the checkpoint process is
opening each file one by one and fsyncing them. Does that make any
difference here? Could you adjust the timing here?
Have a nice day,
--
Martijn van Oosterhout kleptog
, generally.
Have a nice day,
--
Martijn van Oosterhout kleptog@svana.org http://svana.org/kleptog/
From each according to his ability. To each according to his ability to
litigate.
signature.asc
Description: Digital signature
On Tue, Dec 26, 2006 at 12:49:55PM -0500, D'Arcy J.M. Cain wrote:
On Tue, 26 Dec 2006 18:12:45 +0100
Martijn van Oosterhout kleptog@svana.org wrote:
On Tue, Dec 26, 2006 at 12:04:40PM -0500, D'Arcy J.M. Cain wrote:
Now it certainly seems to me that it should behave as described given
these methods?
There's plenty of the comments in the files that implement them (the
executor directory. Have you checked them?
Have a nice day,
--
Martijn van Oosterhout kleptog@svana.org http://svana.org/kleptog/
From each according to his ability. To each according to his ability to
litigate
.
Have a nice day,
--
Martijn van Oosterhout kleptog@svana.org http://svana.org/kleptog/
From each according to his ability. To each according to his ability to
litigate.
signature.asc
Description: Digital signature
,
--
Martijn van Oosterhout kleptog@svana.org http://svana.org/kleptog/
From each according to his ability. To each according to his ability to
litigate.
signature.asc
Description: Digital signature
view definitions or plans.
The number of places needing the logical index are not that man,
relativelyy, and given it has no intrinsic meaning, it's better to give
it a numeric value which is obviously abritrary (like 10001).
Have a nice day,
--
Martijn van Oosterhout kleptog@svana.org http
On Thu, Dec 21, 2006 at 10:50:59AM -0500, Tom Lane wrote:
Martijn van Oosterhout kleptog@svana.org writes:
The thing is, physical index numbers has meaning, the logical index
number does not. In a view definition we're going to store the physical
index, not the logical one, for example
has just been
broken. If the index references physical numbers, everything works
without changes.
Same with views, if you use logical numbers you have to rebuild the
view each time. Why bother, when physical numbers work and don't have
that problem?
Have a nice day,
--
Martijn van Oosterhout
On Thu, Dec 21, 2006 at 11:15:38AM -0500, Tom Lane wrote:
Martijn van Oosterhout kleptog@svana.org writes:
Can we? For anything of any permenence (view definitions, rules,
compiled functions, plans, etc) you're going to want the physical
number, for the same reason we store the oids
day,
--
Martijn van Oosterhout kleptog@svana.org http://svana.org/kleptog/
From each according to his ability. To each according to his ability to
litigate.
signature.asc
Description: Digital signature
a datafile blocks fsyncing the WAL. That
seems terribly unlikely (although...). What OS/Kernel/Filesystem is
this. I note a sync bug in linux for ext3 that may have relevence.
Have a nice day,
--
Martijn van Oosterhout kleptog@svana.org http://svana.org/kleptog/
From each according to his ability
of the problem. AFAICS there's
hardly anywhere that would use physical offsets...
Have a nice day,
--
Martijn van Oosterhout kleptog@svana.org http://svana.org/kleptog/
From each according to his ability. To each according to his ability to
litigate.
signature.asc
Description: Digital
numbers distinct, I'd be all for it.
The only way I can see is to make the domains of the numbers distinct.
Negative vs. positive numbers?
Negative is used by system columns. Just adding some large constant
(say 1) should be enough.
Have a nice day,
--
Martijn van Oosterhout kleptog
the inode via a
full journal commit even if it was unaltered.
However you're running a later version so that's not it.
Have a nice day,
--
Martijn van Oosterhout kleptog@svana.org http://svana.org/kleptog/
From each according to his ability. To each according to his ability to
litigate
also can't be type checked.
If you switched everything over to inline functions you might get it to
work, but that's about it.
IMHO the best solution is to offset the logical numbers by some
constant...
Have a nice day,
--
Martijn van Oosterhout kleptog@svana.org http://svana.org/kleptog/
From
discussion in this direction isn't really useful.
Once this is possible it would allow a lot of simple savings. For
example, shifting all fixed width fields to the front means they can
all be accessed without looping through the previous columns, for
example.
Have a nice day,
--
Martijn van Oosterhout
a single identifier. The
identifier itself does not contain the '.', that's a seperator and so
isn't part of the actual identifier.
Have a nice day,
--
Martijn van Oosterhout kleptog@svana.org http://svana.org/kleptog/
From each according to his ability. To each according to his ability
you may have to
skip a couple to get the real message.
Have a nice day,
--
Martijn van Oosterhout kleptog@svana.org http://svana.org/kleptog/
From each according to his ability. To each according to his ability to
litigate.
signature.asc
Description: Digital signature
is needed by initdb but was not found in the
same directory as
j:/postgres/src/test/regress/./tmp_check/install/postgres/bin/initdb.
No idea about that, the binary *should* be there...
Have a nice day,
--
Martijn van Oosterhout kleptog@svana.org http://svana.org/kleptog/
From each according
it might be a good choice.
I like this one more than opcluster. opfamily has a good ring to it
also.
Have a nice day,
--
Martijn van Oosterhout kleptog@svana.org http://svana.org/kleptog/
From each according to his ability. To each according to his ability to
litigate.
signature.asc
with
definitions needed by system catalogs, so you don't want to allow users
to mess with the btree(int4) class, but you want to allow them to
modify the group as a whole to add new things and remove things they've
added.
Have a nice day,
--
Martijn van Oosterhout kleptog@svana.org http://svana.org/kleptog
to find the list and set it the way you want.
OTOH, postgres never uses timezone identifiers in output, so I'm not sure
why it would need to care.
Have anice day,
--
Martijn van Oosterhout kleptog@svana.org http://svana.org/kleptog/
From each according to his ability. To each according to his
and file it. Should probably
change the timezone identifier to full form.
Have a nice day,
--
Martijn van Oosterhout kleptog@svana.org http://svana.org/kleptog/
From each according to his ability. To each according to his ability to
litigate.
signature.asc
Description: Digital signature
,
they're the same file (at least here).
$ ls -l /usr/lib/libldap.so.2
lrwxrwxrwx 1 root root 14 2005-06-09 10:42 /usr/lib/libldap.so.2 -
libldap_r.so.2
Just make sure you don't add unnecessary dependancies for platforms
other than unixware.
Have a nice day,
--
Martijn van Oosterhout
to calibrate the result. If the CPU goes to
sleep, there's is no way for the userspace process to know. Only the
kernel has all the relevent information about what time is to get a
reasonable result.
Have a nice day,
--
Martijn van Oosterhout kleptog@svana.org http://svana.org/kleptog/
From each
tell you if signals have been lost. Given they are
most likely to be lost during high disk I/O, they're actually
significant. I'm trying to think of a way around that. Then you don't
need a cheap gettimeofday at all...
Have a nice day,
--
Martijn van Oosterhout kleptog@svana.org http://svana.org
how many of the supported platforms fall under that
catagorisation.
Have a nice day,
--
Martijn van Oosterhout kleptog@svana.org http://svana.org/kleptog/
From each according to his ability. To each according to his ability to
litigate.
signature.asc
Description: Digital signature
,
--
Martijn van Oosterhout kleptog@svana.org http://svana.org/kleptog/
From each according to his ability. To each according to his ability to
litigate.
signature.asc
Description: Digital signature
On Fri, Dec 15, 2006 at 09:56:57AM -0500, Tom Lane wrote:
Martijn van Oosterhout kleptog@svana.org writes:
On Fri, Dec 15, 2006 at 12:20:46PM +, Simon Riggs wrote:
Maybe sampling every 10 rows will bring things down to an acceptable
level (after the first N). You tried less than 10
to the
result. There's no point using an index if the result is in the wrong
order for the join, for example.
Have a nice day,
--
Martijn van Oosterhout kleptog@svana.org http://svana.org/kleptog/
From each according to his ability. To each according to his ability to
litigate.
signature.asc
into
something larger. However, there the point was that the group becomes a
common pathkey identifier for all the underlying types, which is not in
your proposal.
Have a nice day,
--
Martijn van Oosterhout kleptog@svana.org http://svana.org/kleptog/
From each according to his ability
sound any good :(
It's good is that this provides more information about the underlying
types to the system, which improves the possibility of optimisation
(and correctness).
Have a nice day,
--
Martijn van Oosterhout kleptog@svana.org http://svana.org/kleptog/
From each according to his
day,
--
Martijn van Oosterhout kleptog@svana.org http://svana.org/kleptog/
From each according to his ability. To each according to his ability to
litigate.
signature.asc
Description: Digital signature
by just looking for an = but I think anything more is
likely to be redundant.
Does that mean that:
psql -d service=myservice
should Just Work(tm)? That would be nice.
Have a nice day,
--
Martijn van Oosterhout kleptog@svana.org http://svana.org/kleptog/
From each according to his
the overhead
of multiple lex/yacc parsers, but you wouldn't have to change the main
parser for every extension.
Has anyone ever heard of something like this?
Have a nice day,
--
Martijn van Oosterhout kleptog@svana.org http://svana.org/kleptog/
From each according to his ability. To each
/local/pg8.1, init
scripts are /etc/init.d/postgres8.1, /etc/init.d/postgres7.4
That's the apporaich the debian packages take too, although they also
add a layer so you can have multiple clusters also, each with whatever
version you like.
Have a ncie day,
--
Martijn van Oosterhout kleptog
of the C
compiler, or it was installed incorrectly, so that part of the project
was built with one version and part with another. Make sure you've got
the C compiler correctly installed and that everything is being
compiled/linked with the same version.
Have a ncie day,
--
Martijn van Oosterhout
this helps,
--
Martijn van Oosterhout kleptog@svana.org http://svana.org/kleptog/
From each according to his ability. To each according to his ability to
litigate.
signature.asc
Description: Digital signature
/bugreport.cgi?bug=351629
Google around, many people have run into this and not nailed down the
problem. At the very least it appears gcc 3.3 is most susceptable. Are
you using straight Debian Stable or a partially upgraded system? Maybe
a full upgrade would help.
Have a ncie day,
--
Martijn van
?
Have a ncie day,
--
Martijn van Oosterhout kleptog@svana.org http://svana.org/kleptog/
From each according to his ability. To each according to his ability to
litigate.
signature.asc
Description: Digital signature
would be affected by this.
Have a ncie day,
--
Martijn van Oosterhout kleptog@svana.org http://svana.org/kleptog/
From each according to his ability. To each according to his ability to
litigate.
signature.asc
Description: Digital signature
is that currently indexes cannot be used to find NULLs
in a table. Patches have been created that cover most index types, but
it's not part of the main distribution.
Partial indexes can be a solution to the x IS NULL clauses.
Hope this helps,
--
Martijn van Oosterhout kleptog@svana.org http
to address
Tom's concerns (other than not indexing IS NOT NULL, which I'm not sure
is all that useful...)
There's been work on it. Theodor cleaned it up for HEAD and looked at
adding GiST support. I beleive he's waiting for 8.2 to release.
Have a nice day,
--
Martijn van Oosterhout kleptog
constructor
and all its parameters are normal SQL expressions, so you can reference
columns and use NULL directly without quotes. The latter is the string
value of the array, which is specially decoded. Thats why the latter
treats the double quotes differently.
Hope this helps,
--
Martijn van
opinion?
Arguably you could give people a choice, say %P for the absolute path
and %p for the relative one. In Unix you can easily prepend $PWD to the
string, but I don't know how easy that is in Windows.
Have a nice day,
--
Martijn van Oosterhout kleptog@svana.org http://svana.org/kleptog
a single unix-like name, and I haven't looked at how
to properly do that translation from SASL (or GSSAPI) names.
Usually a field in the certificate is the username postgresql wants,
which can be mapped via a table. For SASL I don't know.
Have a nice day,
--
Martijn van Oosterhout kleptog
has a valid certificate, but you
can't use it for authentication. AFAIK it just needs to be coded
(certainly the code to get the relevent fields from the certificate is
there).
Have a nice day,
--
Martijn van Oosterhout kleptog@svana.org http://svana.org/kleptog/
From each according to his
needed...
Have a nice day,
--
Martijn van Oosterhout kleptog@svana.org http://svana.org/kleptog/
From each according to his ability. To each according to his ability to
litigate.
signature.asc
Description: Digital signature
, and that's going to messy.
Have a nice day,
--
Martijn van Oosterhout kleptog@svana.org http://svana.org/kleptog/
From each according to his ability. To each according to his ability to
litigate.
signature.asc
Description: Digital signature
-parsetree);
print_plan writes to stdout, did you check where that is redirected to?
Also, I thought there was a logging option to print plans, but I might
be wrong about that.
Have a nice day,
--
Martijn van Oosterhout kleptog@svana.org http://svana.org/kleptog/
From each according to his
there be a
way of detecting a missing 512 byte block in the middle of an 8K block.
The idea of simply writing a serial counter every 512 bytes seems to
be a good way to handle that...
Have a nice day,
--
Martijn van Oosterhout kleptog@svana.org http://svana.org/kleptog/
From each according to his ability
'
usethreads='define'
usemultiplicity='define'
Have a nice day,
--
Martijn van Oosterhout kleptog@svana.org http://svana.org/kleptog/
From each according to his ability. To each according to his ability to
litigate.
signature.asc
Description: Digital signature
/cgi-bin/bugreport.cgi?bug=313219
Which suggest that prior to glibc 2.3.5, posix_fadvise crashed on 2.4
kernels. That's a fairly recent version, so the bug would still be
fairly widespead.
Have a nice day,
--
Martijn van Oosterhout kleptog@svana.org http://svana.org/kleptog/
From each according
for.
Maybe March 2010 we can look into it...
Have a nice day,
--
Martijn van Oosterhout kleptog@svana.org http://svana.org/kleptog/
From each according to his ability. To each according to his ability to
litigate.
signature.asc
Description: Digital signature
, but the data
isn't.
Have a ncie day,
--
Martijn van Oosterhout kleptog@svana.org http://svana.org/kleptog/
From each according to his ability. To each according to his ability to
litigate.
signature.asc
Description: Digital signature
decide how to fix it. So, what is the bottleneck? Is
PostgreSQL unable to max out the I/O bandwidth? Where? Why?
For systems where postgresql is unable to saturate the i/o bandwidth,
this is the proposed solution. Are there others?
Have a nice day,
--
Martijn van Oosterhout kleptog@svana.org http
.)
This appears to be exactly what we want, no? It would be nice to get
some idea of what systems support this.
Have a nice day,
--
Martijn van Oosterhout kleptog@svana.org http://svana.org/kleptog/
From each according to his ability. To each according to his ability to
litigate
it's called after
the system headers, otherwise the problem isn't fixed.
Have a nice day,
--
Martijn van Oosterhout kleptog@svana.org http://svana.org/kleptog/
From each according to his ability. To each according to his ability to
litigate.
signature.asc
Description: Digital signature
you to split a single consecutive read into multiple
buffers. Doesn't help at all for reads on widely areas of a file.
Have a ncie day,
--
Martijn van Oosterhout kleptog@svana.org http://svana.org/kleptog/
From each according to his ability. To each according to his ability to
litigate
a nice day,
--
Martijn van Oosterhout kleptog@svana.org http://svana.org/kleptog/
From each according to his ability. To each according to his ability to
litigate.
signature.asc
Description: Digital signature
also support timezone
'Pacific/Kiritimati' which is at +1400, so I doubt it's an issue.
Wanna send a patch?
Have a nice day,
--
Martijn van Oosterhout kleptog@svana.org http://svana.org/kleptog/
From each according to his ability. To each according to his ability to
litigate.
signature.asc
concatenation.
I would argue it's inconsistant. No other function treats a NULL like
an empty string, so I really don't see why textcat() should.
Have a nice day,
--
Martijn van Oosterhout kleptog@svana.org http://svana.org/kleptog/
From each according to his ability. To each according
the header files to understand what they mean.
Hope this helps,
--
Martijn van Oosterhout kleptog@svana.org http://svana.org/kleptog/
From each according to his ability. To each according to his ability to
litigate.
signature.asc
Description: Digital signature
|| 'bar'= 'bar'
'' || 'bar' = 'bar'
But NULL is not an empty string. Oracle chooses to make NULL and the
empty string the same, we don't. So logically we shouldn't treat them
the same for text concatination either.
Have a nice day,
--
Martijn van Oosterhout kleptog@svana.org http
the algorithm is comparing if r.id equals s.id
The code doing the work is actually ExecScanHashBucket() which is in
nodeHash.c. The actual check is done by the ExecQual there...
Hope this helps,
--
Martijn van Oosterhout kleptog@svana.org http://svana.org/kleptog/
From each according to his
standards where C has to actually be a grouping column).
Have a nice day,
--
Martijn van Oosterhout kleptog@svana.org http://svana.org/kleptog/
From each according to his ability. To each according to his ability to
litigate.
signature.asc
Description: Digital signature
perl5.8. In know the perl5.6 model was different and somewhat more
awkward to use.
Have a nice day,
--
Martijn van Oosterhout kleptog@svana.org http://svana.org/kleptog/
From each according to his ability. To each according to his ability to
litigate.
signature.asc
Description: Digital
lookup that way. If you want that to work, you
should preload a list of timezones and store the list internally.
Another way to deal with start timezone names: we have a table for
looking up EST and such, short names like GMT-0 could be added to
that table...
Have a nice day,
--
Martijn van
day,
--
Martijn van Oosterhout kleptog@svana.org http://svana.org/kleptog/
From each according to his ability. To each according to his ability to
litigate.
signature.asc
Description: Digital signature
On Sun, Oct 15, 2006 at 02:26:12PM -0400, Neil Conway wrote:
On Sun, 2006-10-15 at 19:56 +0200, Martijn van Oosterhout wrote:
Sure, I even implemented it once. Didn't get any faster.
Did you just do something akin to s/read/aio_read/ etc., or something
more ambitious? I think that really
day,
--
Martijn van Oosterhout kleptog@svana.org http://svana.org/kleptog/
From each according to his ability. To each according to his ability to
litigate.
signature.asc
Description: Digital signature
van Oosterhout kleptog@svana.org http://svana.org/kleptog/
From each according to his ability. To each according to his ability to
litigate.
signature.asc
Description: Digital signature
case
you load all the warnings into an environment variable and print that
at the end...
Have a nice day,
--
Martijn van Oosterhout kleptog@svana.org http://svana.org/kleptog/
From each according to his ability. To each according to his ability to
litigate.
signature.asc
Description
states.
Hope this helps,
--
Martijn van Oosterhout kleptog@svana.org http://svana.org/kleptog/
From each according to his ability. To each according to his ability to
litigate.
signature.asc
Description: Digital signature
,
--
Martijn van Oosterhout kleptog@svana.org http://svana.org/kleptog/
From each according to his ability. To each according to his ability to
litigate.
signature.asc
Description: Digital signature
a histogram for the current session
only, or even having profile to select from. I don't think annotating
the query itself is a particularly good idea.
The hard part is stoing the histograms and getting the planner to use
them, once that happens the really is trivial.
Have a nice day,
--
Martijn van
feature.
IIRC it was made a non-fatal warning somewhere near the end of the
output, but I'm not sure...
Have a nice day,
--
Martijn van Oosterhout kleptog@svana.org http://svana.org/kleptog/
From each according to his ability. To each according to his ability to
litigate.
signature.asc
would start by reading the documentation, specifically the part about
GiST. Once you have understood the concept and code there, go to
reading the rtree code in the backend. That should answer almost all
your questions.
Have a nice day,
--
Martijn van Oosterhout kleptog@svana.org http://svana.org
of.
These sorts of things matter.
People are working it, someone even got so far as dealing with most
catalog upgrades. The hard part going to be making sure that even if
the power fails halfway through an upgrade that your data will still be
readable...
Have a nice day,
--
Martijn van Oosterhout kleptog
memory that would take to store...
What were you trying to do?
Have a nice day,
--
Martijn van Oosterhout kleptog@svana.org http://svana.org/kleptog/
From each according to his ability. To each according to his ability to
litigate.
signature.asc
Description: Digital signature
there should be people willing to fund the development.
There have been a few people (even in the last few weeks) who say
they're looking into it, perhaps they need a helping hand?
Someone got as far as handling catalog updates I beleive,
Have a nice day,
--
Martijn van Oosterhout kleptog@svana.org
not. You don't see any messages about the other 100 leaks
found because I figure they're not worth the effort. This function is
used widely enough and a simple enough fix that I figured I might be
worth fixing.
Have a nice day,
--
Martijn van Oosterhout kleptog@svana.org http://svana.org/kleptog
On Tue, Oct 03, 2006 at 04:34:06PM +0200, Magnus Hagander wrote:
search=# select to_tsquery('foo bar');
ERROR: syntax error
Seems to me, at the very least, the message should be:
ERROR: tsearch: syntax error
Then people have an idea where it comes from.
Have a nice day,
--
Martijn van
Just a minor thing. In yesno_prompt(), the value is resp is allocated
memory that is never freed.
File: src/bin/scripts/common.c
Line: 218
Not terribly important though, it's not used in critical utilities, but
it's used often.
Found by coverity.
--
Martijn van Oosterhout kleptog@svana.org
601 - 700 of 1563 matches
Mail list logo
