From: Tom Lane [mailto:[EMAIL PROTECTED]
Bruce Momjian pgman@candle.pha.pa.us writes:
Jim C. Nasby wrote:
On Sat, Aug 13, 2005 at 06:24:01PM -0400, Tom Lane wrote:
IIRC, what we actually intended that to mean is the time
of receipt of
the current interactive command --- that is, it
Message-
From: Tom Lane [mailto:[EMAIL PROTECTED]
Sent: Monday, August 22, 2005 2:58 PM
To: Jim Nasby
Cc: Bruce Momjian; Michael Fuhr; pgsql-hackers@postgresql.org
Subject: Re: [HACKERS] psql SET/RESET/SHOW tab completion
Jim C. Nasby [EMAIL PROTECTED] writes:
What about going
-Original Message-
From: Tom Lane [mailto:[EMAIL PROTECTED]
Sent: Monday, August 22, 2005 3:18 PM
To: Jim Nasby
Cc: Bruno Wolff III; William ZHANG; pgsql-hackers@postgresql.org
Subject: Re: [HACKERS] CREATE USER and pg_user
Jim C. Nasby [EMAIL PROTECTED] writes:
On Fri, Aug
-Original Message-
From: Bruce Momjian [mailto:[EMAIL PROTECTED]
Sent: Wednesday, August 24, 2005 3:40 PM
To: Robert Treat
Cc: pgsql-hackers@postgresql.org; Jim Nasby; Greg Stark; Tom Lane
Subject: Re: [HACKERS] TODO questions
Robert Treat wrote:
I've always been
-Original Message-
From: Magnus Hagander [mailto:[EMAIL PROTECTED]
Sent: Thursday, August 25, 2005 1:31 PM
To: Jim Nasby
Cc: Marc G. Fournier; pgsql-hackers@postgresql.org
Subject: RE: [HACKERS] Stuff running slooow
Well, if hardware or bandwidth becomes an issue I suspect
From: Andrew Dunstan [mailto:[EMAIL PROTECTED]
Also, as nifty as this might be, we should also be prepared
for people
to complain that it runs a lot slower than vanilla COPY, because it
surely will.
At which point we point out to them that it's also much faster than any of the
other
Adding -hackers back to the list...
-Original Message-
From: Gregory Maxwell [mailto:[EMAIL PROTECTED]
Sent: Thursday, October 27, 2005 5:03 PM
To: Jim Nasby
Subject: Re: [HACKERS] enums
On 10/27/05, Jim C. Nasby [EMAIL PROTECTED] wrote:
On Thu, Oct 27, 2005 at 04:54:36PM
From: Tom Lane [mailto:[EMAIL PROTECTED]
Jim C. Nasby [EMAIL PROTECTED] writes:
What has been happening is periodic random crashes, around
1 a week. I
now have a good core for one, as well as an assert:
TRAP: FailedAssertion(!(shared-page_number[slotno] == pageno
From: Tom Lane [mailto:[EMAIL PROTECTED]
Jim C. Nasby [EMAIL PROTECTED] writes:
On Fri, Oct 28, 2005 at 05:45:51PM -0400, Tom Lane wrote:
Jim, are you interested
in seeing if this patch makes the problem go away for you?
Well, this is a production system... what's the risk with
that
Ooops, fat-finger'd -hackers...
-Original Message-
Adding -hackers back to the list.
From: Leandro Guimarães Faria Corcete Dutra
Em Seg, 2006-01-16 às 12:52 -0600, Jim C. Nasby escreveu:
On Sat, Jan 14, 2006 at 07:28:21PM +0900, Michael Glaesemann wrote:
For UPDATEs and
: Wednesday, March 01, 2006 12:48 PM
To: Jim Nasby
Subject: Rép. : Re: [PERFORM] Bad plan on a view ([Congés])
Actuellement en congés, je serais de retour le 6/03/2006
En cas de problème bloquant, veuillez contacter Gilles Pierret.
---(end of broadcast
On Mar 25, 2006, at 4:14 PM, Tom Lane wrote:
Jim C. Nasby [EMAIL PROTECTED] writes:
On Fri, Mar 24, 2006 at 10:49:00PM -0500, Tom Lane wrote:
I think we've got that one actually. It's domains as PL-function
output
types that aren't checked. Also plpgsql fails to enforce domain
checks
on
On Apr 2, 2006, at 6:13 PM, Tom Lane wrote:
Jonah H. Harris [EMAIL PROTECTED] writes:
On 4/2/06, Tom Lane [EMAIL PROTECTED] wrote:
If you're expecting that you'll be able to write BYTEA(n) and avoid
storing a length word, you'll find that it's not a trivial matter.
It may not be trivial,
If nothing else, any of the 'beginner todo' items are likely
candidates, though I suspect none of them individually are enough
work for an entire summer.
If no one beats me to it, I'll try and compile a list of likely TODOs
for this.
On Apr 5, 2006, at 12:16 AM, Josh Berkus wrote:
be looked at that are sort of
3rd party
projects, should we attempt to collaborate on putting up a list
some place?
Robert Treat
On Wednesday 05 April 2006 11:22, Jim Nasby wrote:
If nothing else, any of the 'beginner todo' items are likely
candidates, though I suspect none of them individually
after exams finish.
Please post something about where we can find this TODO list when
it is available.
Thanks,
Nathan
On 4/5/06, Jim Nasby [EMAIL PROTECTED] wrote: If nothing else,
any of the 'beginner todo' items are likely
candidates, though I suspect none of them individually are enough
-bugs is getting inundated with windows installer bugs, and people on
the list don't seem to be replying to them. Can someone with the
installer project add more prominent information about where users
should be reporting installer bugs to? (I'm guessing that the
installer has a bug
Can someone drop this puppy?
-Original Message-
From: System Administrator
Sent: Thursday, April 06, 2006 11:49 PM
To: [EMAIL PROTECTED]
Subject: Undeliverable:Re: [GENERAL] stored proc vs sql query string
Your message did not reach some or all of the intended
I often find myself wanting to know how many transactions per second
a database is committing to disk, as well as how many queries per
second it's processing. While Larry's busy making stats changes, I'd
like to propose a few more counters:
Number of commits: Ideally, this would only count
On May 25, 2006, at 11:24 AM, Andreas Pflug wrote:
BTW, I don't actually understand why you want this at all. If you're
not going to keep a continuing series of WAL files, you don't have
any
PITR capability. What you're proposing seems like a bulky,
unportable,
hard-to-use equivalent of
Now that we've got a nice amount of tuneability in the bgwriter, it
would be nice if we had as much insight into how it's actually doing.
I'd like to propose that the following info be added to the stats
framework to assist in tuning it:
bgwriter_rounds - number of rounds that have run
On Jun 2, 2006, at 10:27 AM, Andrew Dunstan wrote:
Joshua D. Drake wrote:
Tom Lane wrote:
Andrew Dunstan [EMAIL PROTECTED] writes:
What's happening here is that cvs actually creates the directory
and then later prunes it when it finds it is empty.
I find that explanation pretty
On Jun 2, 2006, at 5:24 PM, Todd A. Cook wrote:
Josh Berkus wrote:
Greg, Tom,
But for most users analyze doesn't really have to run as often as
vacuum. One sequential scan per night doesn't seem like that big
a deal
to me.
Clearly you don't have any 0.5 TB databases.
Perhaps something
On Jun 3, 2006, at 2:05 PM, Nicolai Petri wrote:
On Saturday 03 June 2006 17:27, Tom Lane wrote:
PFC [EMAIL PROTECTED] writes:
[snip - complicated update logic proprosal]
What do you think ?
Sounds enormously complicated and of very doubtful net win --- you're
[snip - ... bad
On Jun 4, 2006, at 5:09 PM, Tom Lane wrote:
Greg Stark [EMAIL PROTECTED] writes:
Hannu Krosing [EMAIL PROTECTED] writes:
Ühel kenal päeval, L, 2006-06-03 kell 10:43, kirjutas Jim Nasby:
Might also be worth adding analyze delay settings, ala
vacuum_cost_delay.
ANALYZE already respects
On Jun 3, 2006, at 10:27 AM, Tom Lane wrote:
PFC [EMAIL PROTECTED] writes:
What do you think ?
Sounds enormously complicated and of very doubtful net win --- you're
moving a lot of overhead into SELECT in order to make UPDATE cheaper,
and on top of that the restriction to same-page
On Jun 4, 2006, at 8:18 AM, Andrew Dunstan wrote:
I said:
Another option would be to re-run cvs up one more time if we get any
unexpected files. It sounds like that would fix this issue on
windows
machines, while still ensuring we had a clean repo to work from.
please see the new
On Jun 12, 2006, at 10:38 AM, Kris Kennaway wrote:
FYI, the biggest source of contention is via semop() - it might be
possible to optimize that some more in FreeBSD, I don't know.
Yeah, I've seen PostgreSQL on FreeBSD fall over at high load with
a lot
of procs in either semwait or semlock.
On Jun 15, 2006, at 9:45 PM, Toru SHIMOGAKI wrote:
NTT has some ideas about index creation during a large amount of
data loading. Our approach is the following: index tuples are
created at the same time as heap tuples and added into heapsort. In
addition, we use old index tuples as sorted
Moving to osdldbt-general and dropping Tom and Marc.
On Jun 13, 2006, at 1:18 PM, Kris Kennaway wrote:
On Tue, Jun 13, 2006 at 12:29:14PM -0500, Jim C. Nasby wrote:
Unless supersmack has improved substantially, you're unlikely to find
much interest. Last I heard it was a pretty brain-dead
On Jun 13, 2006, at 9:42 PM, Kris Kennaway wrote:
BTW, there's another FBSD performance odditiy I've run across.
Running
pg_dump -t email_contrib -COx stats | bzip2 ec.sql.bz2
which dumps the email_contrib table to bzip2 then to disk, the OS
won't use more than 1 CPU on an SMP system...
On Jun 16, 2006, at 12:01 PM, Josh Berkus wrote:
Folks,
I am thrill to inform you all that Sun has just donated a fully
loaded
T2000 system to the PostgreSQL community, and it's being setup by
Corey
Shields at OSL (osuosl.org) and should be online probably early next
week. The system has
On Jun 16, 2006, at 12:01 PM, Josh Berkus wrote:
First thing as soon as I have a login, of course, is to set up a
Buildfarm
instance.
Keep in mind that buildfarm clients and benchmarking stuff don't
usually mix well.
--
Jim C. Nasby, Sr. Engineering Consultant [EMAIL PROTECTED]
On Jun 22, 2006, at 12:56 PM, Greg Stark wrote:
Just for the record, if i understood correctly -- this was all a
bit black
magicky -- Oracle found the data in the rollback segment by storing
a pointer
to it in the block header where the updated data is. Ie, it could jump
straight to the
On Jun 22, 2006, at 2:00 PM, Mark Woodward wrote:
I actually have a good number of years of experience in this topic,
and
memcached or file system files are NOT the best solutions for a server
farm.
What's wrong with memcached for session data?
--
Jim C. Nasby, Sr. Engineering Consultant
On Jun 22, 2006, at 1:09 PM, Tom Lane wrote:
Lukas Smith [EMAIL PROTECTED] writes:
Jochem van Dieten wrote:
make the session handler smarter? And if you can't do that, put some
logic in the session table that turns an update without changes
into a
no-op?
err isnt that one the job of the
On Jul 4, 2006, at 3:35 AM, Dave Page wrote:
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Neil Conway
Sent: 04 July 2006 05:53
To: pgsql-hackers@postgresql.org
Subject: [HACKERS] system info functions
(1) The docs claim that pg_get_viewdef() returns
ISTM that pg_dump needs to produce output that includes schema names,
though I'm not sure what side-effects that would have. I know one
issue is that it'd make it next to impossible to move things to a
different schema just be editing the dump.
On Jul 5, 2006, at 9:47 AM, Phil Frost wrote:
On Jul 6, 2006, at 11:02 AM, Phil Frost wrote:
I hope the above example is strong enough to elicit a comment from a
qualified developer. If it is not, consider that stored procedures
contain prepared statements, and many client applications cache
prepared
statements as well. Thus, revoking
On Jul 6, 2006, at 4:02 PM, Thomas Hallgren wrote:
In answer to your question, though my opinion carries no special
weight at
all, I would suggest adding a bare bones 16-byte data type to core
and a
second binary-compatible data type based on it that parsed/output
as uuids.
The extended
On Jul 17, 2006, at 2:48 PM, Zdenek Kotala wrote:
Josh Berkus wrote:
Zdenek,
I would like to implement Mark change-on-restart-only values in
postgresql.conf item. Anybody works on this? Does it mean add extra
comment to postgresql.conf for variable which has PG_POSTMASTER
context?
Somehow I
On Jul 16, 2006, at 3:08 PM, Andrew Dunstan wrote:
Kris Jurka wrote:
For my cygwin buildfarm member I setup cron, but the make step
failed for every build for unknown reasons while succeeding if not
run from cron.
Is this still happening? We should try to get to the bottom of it.
Try
You should submit to -patches; at least that it should either get
into the queue or you should get a reason why it didn't.
On Jul 17, 2006, at 4:27 PM, Martin Pitt wrote:
some time ago I started a discussion [1] here about modifying pg_dump
to not restore TABLE DATA objects if the
On Jul 21, 2006, at 9:03 AM, Tom Lane wrote:
One
possibility is that early freeze is at 1B transactions and we push
forced-freeze back to 1.5B transactions (the current forced-freeze
at 1B
transactions seems rather aggresive anyway, now that the server will
refuse to issue new commands rather
On Jul 27, 2006, at 7:30 AM, Tom Lane wrote:
Susanne Ebrecht [EMAIL PROTECTED] writes:
... We could provide the mixed update syntax and leave the
typed row value expression for the next release. Do you agree?
I don't really see the point --- the patch won't provide any new
functionality in
On Jul 27, 2006, at 9:16 AM, Bort, Paul wrote:
Peter Eisentraut wrote:
I have committed it using the 1024 multiplier, but if you want to
propose changing all uses of kB, MB, and GB in PostgreSQL to
the other
system, now would be the time to do it.
I think it would be a good idea. I know I
On Jul 25, 2006, at 3:31 PM, Tom Lane wrote:
Hannu Krosing [EMAIL PROTECTED] writes:
Ühel kenal päeval, T, 2006-07-25 kell 13:06, kirjutas Tom Lane:
The reason I have such high sales resistance is that we've
carried the
hash and rtree AMs for years, hoping that someone would do the
work to
Actually, -general would be the place. -hackers is for back-end hacking.
On Jul 26, 2006, at 1:18 PM, Redefined Horizons wrote:
Is this an appropriate place for questions about implementing user
defined functions and custom data types in the C programming language?
I didn't want to dirty the
On Jul 26, 2006, at 4:29 PM, Hannu Krosing wrote:
Well the desire for it comes from a very well established need
for dealing
with extremely large tales with relatively small hot spots. The
basic problem
being that currently the cost of vacuum is proportional to the
size of the
table rather
On Jul 26, 2006, at 10:29 AM, Tom Lane wrote:
Gregory Stark [EMAIL PROTECTED] writes:
... Well it's not like the existing vacuum checks for this.
Right, that's exactly why the patch works at all. But the point
here is
that the existing vacuum does not rely on re-computing index keys; all
On Jul 28, 2006, at 5:05 PM, Hannu Krosing wrote:
Ühel kenal päeval, R, 2006-07-28 kell 12:38, kirjutas Jim C. Nasby:
There are other transactions to consider: user transactions that will
run a long time, but only hit a limited number of relations. These
are
as big a problem in an OLTP
Oh, I didn't realize there was a CVSup server. I think it'd be good
to promote that over CVS, as it's (supposedly) much easier on the
hosting machine.
Andrew, is there a way to get the buildfarm to use cvsup instead of
cvs? Does the script just call cvs via the shell?
On Aug 9, 2006, at
On Aug 10, 2006, at 12:29 PM, alfranio correia junior wrote:
One of the great things about Oracle is that they expose a hell of
a lot
of the technology they use to build features like replication; ie:
take
a look at DBMS_*.
If I am not wrong such procedures are only for administrative
First, +1 on Josh B.'s point about trying out Trac, since it's
already up and running. Josh D., can you just turn that on? (BTW, is
trac linked off http://commandprompt.com anywhere? I had to google to
find it yesterday...)
On Aug 9, 2006, at 11:34 PM, Tom Lane wrote:
Mark Kirkwood [EMAIL
On Aug 10, 2006, at 7:57 AM, Tom Lane wrote:
Anyway, after further thought I've concluded that we really should
supply something that returns the Insert pointer, as this would be
useful for debugging and system-monitoring purposes. It's clear
however
that we also need something that returns
On Aug 17, 2006, at 4:10 PM, Martijn van Oosterhout wrote:
On Thu, Aug 17, 2006 at 02:54:20PM -0500, Jim C. Nasby wrote:
On Thu, Aug 17, 2006 at 02:23:48PM +0200, Martijn van Oosterhout
wrote:
On Thu, Aug 17, 2006 at 12:55:28PM +0900, ITAGAKI Takahiro wrote:
But the method has the above
On Aug 17, 2006, at 3:40 PM, Alvaro Herrera wrote:
The searching capabilities in debbugs are, well, non-existent,
which is
a real problem in my mind.
Well, we can set up our own indexing, like Oleg and Teodor have
done in
http://www.pgsql.ru/
That seems like quite a hack for something
Adding -hackers back in...
-Original Message-
From: Chahine Hamila [mailto:[EMAIL PROTECTED]
Sent: Fri 8/25/2006 8:36 PM
To: Jim Nasby
Subject: Re: [HACKERS] integration of pgcluster into postgresql
First, you need to review all the past discussion
about the very
intentional decision
to be
toasted before it normally would could drastically improve tuple
density without requiring the developer to use a 'side table' to
store the data.
--
Jim Nasby[EMAIL PROTECTED]
EnterpriseDB http://enterprisedb.com 512.569.9461 (cell
days, so that even if
someone did get something malicious in there it wouldn't last long.
--
Jim Nasby[EMAIL PROTECTED]
EnterpriseDB http://enterprisedb.com 512.569.9461 (cell)
---(end of broadcast
buffer partitions pointless?
--
Jim Nasby[EMAIL PROTECTED]
EnterpriseDB http://enterprisedb.com 512.569.9461 (cell)
---(end of broadcast)---
TIP 5: don't forget to increase your free space map
it would be nice if the docs adopted
the standard of
CREATE FUNCTION my_function ... $my_function$
...
$my_function$
While more verbose than $$, it does a lot to help code readability.
--
Jim Nasby[EMAIL PROTECTED]
EnterpriseDB http
stuff in postgresql.conf
anyway...
--
Jim Nasby[EMAIL PROTECTED]
EnterpriseDB http://enterprisedb.com 512.569.9461 (cell)
---(end of broadcast)---
TIP 5: don't forget to increase your free space
to the end of the last element of
the mantissa
rather than the first digit so that integers don't need an exponent.
How would that help? If I'm understanding correctly you're just
talking about storing how many places after the decimal instead of
how many in front of it?
--
Jim Nasby
and insert them into
the unique index.
Isn't that what a deferred constraint normally does?
I suspect that your change adds a non-trivial overhead, which means
we don't want it to be the normal case.
--
Jim Nasby[EMAIL PROTECTED]
EnterpriseDB http
://www.commandprompt.com/
--
Jim Nasby[EMAIL PROTECTED]
EnterpriseDB http://enterprisedb.com 512.569.9461 (cell)
---(end of broadcast)---
TIP 3: Have you checked our extensive FAQ?
http
setting to the various options?
Probably not.
If not, do psql users out there feel this is worth a feature
request?
I think so.
---(end of
broadcast)---
TIP 2: Don't 'kill -9' the postmaster
--
Jim Nasby
a function that did, though.
And how I can confirm this?
Trial and error?
Greg
--
See complete headers for address and phone numbers.
--
Jim Nasby[EMAIL PROTECTED]
EnterpriseDB http://enterprisedb.com 512.569.9461 (cell
want to be very careful building and
executing code from the patch queue.
Of course not, but there's any number of ways we could handle that
problem.
pgp signed patches?
Just one possibility. Submitting the patches via a web page that you
have to log into is another.
--
Jim Nasby
meet the least surprise test, but
it does protect newbies which I feel is more important in this case.
--
Jim Nasby[EMAIL PROTECTED]
EnterpriseDB http://enterprisedb.com 512.569.9461 (cell)
---(end of broadcast
is
indeterminate.
CONTEXT: PL/pgSQL function test line 4 at return
--
Jim Nasby[EMAIL PROTECTED]
EnterpriseDB http://enterprisedb.com 512.569.9461 (cell)
---(end of broadcast)---
TIP 4: Have you
and withholding info. I'd
rather see us explicitly state which is preferred and why.
BTW, another confusing example is all the string functions that are
essentially the same, such as substring and substr. (http://
www.postgresql.org/docs/8.1/interactive/functions-string.html)
--
Jim Nasby
On Oct 2, 2006, at 9:17 PM, Bruce Momjian wrote:
Jim Nasby wrote:
On Oct 2, 2006, at 8:41 PM, Bruce Momjian wrote:
David E. Wheeler wrote:
On Sep 28, 2006, at 16:39, Jim C. Nasby wrote:
+1. I was just at a client today that had run into this problem.
Actually, I'm in favor of refusing
, but we might need a form of backwards
compatibility for a version or two...
--
Jim Nasby[EMAIL PROTECTED]
EnterpriseDB http://enterprisedb.com 512.569.9461 (cell)
---(end of broadcast)---
TIP 1: if posting
On Oct 5, 2006, at 9:30 AM, Pavel Stehule wrote:
With func oid I can get all other info later, without it, I need
estimate which functions are in stack track.
Why do you need the OID to know exactly what function something is?
What's wrong with schema.function(args)?
--
Jim Nasby
and clarify the docs on this.
--
Jim Nasby[EMAIL PROTECTED]
EnterpriseDB http://enterprisedb.com 512.569.9461 (cell)
---(end of broadcast)---
TIP 5: don't forget to increase your free space map settings
.
--
Jim Nasby[EMAIL PROTECTED]
EnterpriseDB http://enterprisedb.com 512.569.9461 (cell)
---(end of broadcast)---
TIP 1: if posting/reading through Usenet, please send an appropriate
subscribe
looking at between this and
discussion of visibility changes, etc. is essentially re-designing
the entire storage layout (for better or for worse).
--
Jim Nasby[EMAIL PROTECTED]
EnterpriseDB http://enterprisedb.com 512.569.9461 (cell
with the SQL standard, as well as with other
Databases might be a reason.
It would be nice to denote types/aliases that are and aren't ANSI. A
number are marked in the docs, but it would be good to add the info
to that summary table.
--
Jim Nasby[EMAIL
program that uses a cursor. :-(
IIRC, 8.2 adds the ability to at least copy from a view, if not a raw
SELECT, so you should probably do that instead. Plus it'd be good to
bang on 8.2 with that data set. :) You'll also likely get better
performance.
--
Jim Nasby
with schema.function(args)?
--
oid is simply unique. I can take source code, args and all without
parsing. It's only one difference. I unlike parsing.
decibel=# select 'pg_catalog.abstimelt
(abstime,abstime)'::regprocedure::oid;
oid
-
253
--
Jim Nasby
On Jan 7, 2010, at 4:07 PM, Josh Berkus wrote:
Building a simple solution which doesn't initially cover all bases but
can be steadily improved is a far superior strategy to trying to spec
The Perfect Solution before even starting work. And if we want to keep
recruiting new contributors,
I noticed odd stuff showing up when I fired up an 8.3 psql after using psql in
HEAD. It shows up in .psql_history as well:
deci...@platter.1[20:32]~:5%tail -n 2 .psql_history
\134df+\040tools.raise_exception
\df+ tools.raise_exception
deci...@platter.1[20:35]~:6%
(last entry is from the 8.3
Why does warn; in plperl log as NOTICE in Postgres?
On a related note, what's the logic behind perl DEBUG logging as DEBUG2 instead
of DEBUG1 or DEBUG5? Still seems kind of odd, but at least nowhere near as
surprising as warn becoming NOTICE...
--
Jim C. Nasby, Database Architect
On Jan 21, 2010, at 4:02 PM, Eric B. Ridge wrote:
On Jan 21, 2010, at 12:35 PM, David E. Wheeler wrote:
And where do you think baby powder comes from? Sheesh.
You won the thread!
Heh, who's the wise guy that posted the second comment on
On Jan 13, 2010, at 9:32 PM, Tom Lane wrote:
Jim Nasby deci...@decibel.org writes:
I noticed odd stuff showing up when I fired up an 8.3 psql after using psql
in HEAD. It shows up in .psql_history as well:
Platform? readline version?
This is on snow leopard. FWIW it's still doing
On Apr 16, 2010, at 4:56 PM, Robert Haas wrote:
From reading this and other threads, I think I generally understand
that the perils of setting shared_buffers too high: memory is needed
for other things, like work_mem, a problem which is exacerbated by the
fact that there is some double
On Apr 24, 2010, at 12:31 PM, Tom Lane wrote:
Robert Haas robertmh...@gmail.com writes:
At least AIUI, the use case for this feature is that you want to avoid
creating the same temporary table over and over again.
The context that I've seen it come up in is that people don't want to
clutter
On Apr 24, 2010, at 8:14 PM, Robert Haas wrote:
One possibility: rename the existing pg_stats to pg_stats_permanent. Create
a global temporary table called pg_stats_temporary. pg_stats becomes a union
of the two. I know the backend wouldn't be able to use the view, but
hopefully access to
On Apr 24, 2010, at 10:02 PM, Tom Lane wrote:
Robert Haas robertmh...@gmail.com writes:
Pushing it into the RelFileNode has some advantages in terms of being
able to get at the information from everywhere, but one thing that
makes me think that's probably not a good decision is that we
On Apr 2, 2010, at 12:12 PM, Tom Lane wrote:
Alexey Klyukin al...@commandprompt.com writes:
Is there a reason why only a table free SQL functions are allowed to
be inlined ? I wonder why a simple SQL function containing only a
SELECT * FROM table can't be expanded inline ?
If you're
On Mar 29, 2010, at 11:47 AM, Pavel Stehule wrote:
2010/3/29 Tom Lane t...@sss.pgh.pa.us:
Pavel Stehule pavel.steh...@gmail.com writes:
can we add well structured information about function id and lineno to
ErrorData?
The idea that I was toying with was to report the function OID and line
On Apr 25, 2010, at 2:13 PM, Tom Lane wrote:
Jim Nasby deci...@decibel.org writes:
On Apr 2, 2010, at 12:12 PM, Tom Lane wrote:
If you're thinking of just replacing the call with a sub-SELECT
construct, that's no good in general because it would change the
semantics.
Since Alexey
On May 15, 2010, at 12:05 PM, Heikki Linnakangas wrote:
What exactly is the user trying to monitor? If it's how far behind is
the standby, the difference between pg_current_xlog_insert_location()
in the master and pg_last_xlog_replay_location() in the standby seems
more robust and well-defined
On May 6, 2010, at 4:31 AM, Florian Pflug wrote:
The use case for this was there were different news items,
and there were another table for summaries, that could point
to any of the news items table. Another use case could be
a large partitioned table with an FK to the main table where
the
On May 6, 2010, at 10:24 PM, Robert Haas wrote:
On Tue, May 4, 2010 at 3:03 PM, Alvaro Herrera
alvhe...@commandprompt.com wrote:
[smgr.c,inval.c] Do we need to call CacheInvalidSmgr for temporary
relations? I think the only backend that can have an smgr reference
to a temprel other than the
On May 4, 2010, at 3:48 PM, Gurjeet Singh wrote:
There are quite a few GUC parameters that need restart. Is there a way we can
avoid some of them needing restart? I am specifically looking at archive_mode
and the new wal_level.
For archive_mode you should check the archives; where was
On Apr 29, 2010, at 3:20 PM, Tom Lane wrote:
Simon Riggs si...@2ndquadrant.com writes:
Objections to commit?
This is not the time to be hacking stuff like this. You haven't even
demonstrated that there's a significant performance issue here.
I tend to agree that this point of the cycle
On May 6, 2010, at 4:29 PM, Merlin Moncure wrote:
On Thu, May 6, 2010 at 3:23 PM, Andrew Dunstan and...@dunslane.net wrote:
And many places regard select * in anything other than throw-away queries
as bad practice anyway. I have seen people get bitten by it over and over
again, and I have
On Mar 25, 2007, at 12:31 PM, Tom Lane wrote:
Jim Nasby [EMAIL PROTECTED] writes:
On Mar 21, 2007, at 5:11 AM, Tom Lane wrote:
constraint_exclusion
Hrm... wasn't that option added in case there was a bug in the
exclusion code?
Well, the bug was a lack of ways to get rid of plans that were
1 - 100 of 2196 matches
Mail list logo
