"Eric B. Ridge" <[EMAIL PROTECTED]> writes:
> Wow, thanks for spending the time on this. What about for gettuple?
> Do calls to it take advantage of the cache? If not, this likely
> explains some of my custom am's performance troubles.
gettuple is looked up once at the start of a scan, so the
On Jan 18, 2004, at 7:28 PM, Tom Lane wrote:
Theory B would be that there's some huge overhead in calling
non-built-in functions on your platform.
I've done some profiling and convinced myself that indeed there's
pretty
steep overhead involved in fmgr_info() for a "C"-language function.
Much of i
>> Theory B would be that there's some huge overhead in calling
>> non-built-in functions on your platform.
I've done some profiling and convinced myself that indeed there's pretty
steep overhead involved in fmgr_info() for a "C"-language function.
Much of it isn't platform-dependent either --- a
Pete wrote:
> I am aware that if you enclose those table and column names with "
> then postgresql will take the case into consideration. Only problem
> is most people who have current MySQL project have not written their
> statements with " (MySQL parser uses no quotes of the ` back tick)
> and it
On Thu, 15 Jan 2004, Pete wrote:
> Hi,
>
> I'm not sure if this is the correct place to make a feature request. If
> not hopefully I can be kindly pointed in that direction.
>
> I have several project that use MySQL and I would like to port them to
> PostgreSQL unfortunately they use a naming
Maxim Kovgan wrote:
> hello, i am in the middle of translating this ru.po file into hebrew
> messages.i simply change the garbage with hebrew equivalent.
>
> where shall i send the result to ?
Read this for instructions:
http://developer.postgresql.org/~petere/nlsinfo/
You should probably transl
On Thu, Jan 15, 2004 at 10:02:34PM -0500, Pete wrote:
> Hi,
>
> I'm not sure if this is the correct place to make a feature request. If
> not hopefully I can be kindly pointed in that direction.
>
> I have several project that use MySQL and I would like to port them to
> PostgreSQL unfortunatel
> As of 7.4, this is a requirement badly in need of reconsideration.
> What makes you think there is any function name involved? Consider
> something like
> create index i on t ((col + 2));
>
> Getting the column names is still a sensible operation though. I'd
> suggest looking in pg_depen
hello, i am in the middle of translating this ru.po file into hebrew
messages.i simply change the garbage with hebrew equivalent.
where shall i send the result to ?
Cheers.
M.
---(end of broadcast)---
TIP 8: explain analyze is your friend
Hi,
I'm not sure if this is the correct place to make a feature request. If
not hopefully I can be kindly pointed in that direction.
I have several project that use MySQL and I would like to port them to
PostgreSQL unfortunately they use a naming convention which uses upper
case and lower case
A simple documentation enhancement request: please provide "Fast
Backward"/"Forward" links at the bottom of the page as well.
---(end of broadcast)---
TIP 9: the planner will ignore your desire to choose an index scan if your
joining column's d
The vacuum delay patch is not the ideal solution but it worked like a charm
on my servers. I really need the vacuum delay patch or a better solution in
7.5. I'm getting millions of requests a month and running VACUUM without the
patch makes PostgreSQL useless for many consecutive hours. Not quite t
Any chance we'll see the VACUUM delay patch (throttle) get into 7.5? I only
had the chance to try the first patch by Tom Lane and it was very good
already. I was hoping it gets into 7.4.1 but it didn't. :-(
I really need the VACUUM delay patch because my servers are begging to die
every time VACUU
On Fri, Jan 16, 2004 at 12:00:08PM -0500, Michael Brusser wrote:
> Is there a way to force database to load
> a frequently-accessed table into cache and keep it there?
If it is frequently accessed, I guess it would be in the cachke
permanently
--
Hello,
Are update statements like:
update t1 set (f1, f2, f3) = (select t1, t2, t3 from tab1 where id=5) where id=3
standard. Any hope of supporting this in Postgres?
-Edwin S. Ramirez-
---(end of broadcast)---
TIP 9: the planner will ignore yo
15 matches
Mail list logo
