Per Jensen wrote:
List,
First of all, I am not sure this list is the right one to write to.
I am trying out the postgresql 8.2.beta1 with the jdbc driver contained
in '
postgresql-8.2dev-503.jdbc3.jar' downloaded from 'jdbc.postgresql.org'.
The database is accessed through iBatis version
I've posted a 6.5kB patch (as an attachment) three times over the
past few days but haven't seen it hit the lists. Checking to see if
this goes through.
Did you by any chance gzip it? IIRC, mails with gzipped attachments are
silently dropped on- patches for some reason. (Can't remember if it
Sorry for the delayed response.
Robert Treat wrote:
Looking through -patches I don't see the doc patch, and outside of
installation.sgml there doesn't seem to be anything either. Robert, are you
still on the hook for these?
Josh will help submit the doc patch. I have documented the usage
Peter Eisentraut wrote:
Robert Treat wrote:
Also should installation.sgml
mention the issueswith building 32 vs 64 bit binaries
I'm not convinced there is an issue. dtrace will build the right
binaries by default. If you're messing with mixed environments *and*
delve into dtrace,
TL == Tom Lane [EMAIL PROTECTED] writes:
TL (I suppose it wouldn't work in Windows for lack of hard links, but
TL anyone trying to run a terabyte database on Windows deserves to
TL lose anyway.)
Windows has hard links on NTFS, they are just rarely used.
/Benny
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Benny Amorsen
Sent: 10 October 2006 13:02
To: pgsql-hackers@postgresql.org
Subject: Re: [HACKERS] Upgrading a database dump/restore
TL == Tom Lane [EMAIL PROTECTED] writes:
TL (I suppose it
TL (I suppose it wouldn't work in Windows for lack of hard
links, but
TL anyone trying to run a terabyte database on Windows deserves
to
TL lose anyway.)
Windows has hard links on NTFS, they are just rarely used.
We use them in PostgreSQL to support tablespaces.
No, we don't. We
-Original Message-
From: Magnus Hagander [mailto:[EMAIL PROTECTED]
Sent: 10 October 2006 13:23
To: Dave Page; Benny Amorsen; pgsql-hackers@postgresql.org
Subject: RE: [HACKERS] Upgrading a database dump/restore
TL (I suppose it wouldn't work in Windows for lack of hard
If archive_timeout is set to non 0, it seems an archive log segment is
created every time checkpoint occurs even there's no database
updation. This leads to creating 16MB log segment files every 5
minutes (default checkpoint period), which will in turn produce 4.6GB
log segments with bogus
If archive_timeout is set to non 0, it seems an archive log segment is
created every time checkpoint occurs even there's no database
updation. This leads to creating 16MB log segment files every 5
minutes (default checkpoint period), which will in turn produce 4.6GB
log segments with bogus data.
Tatsuo Ishii [EMAIL PROTECTED] writes:
If archive_timeout is set to non 0, it seems an archive log segment is
created every time checkpoint occurs even there's no database
updation. This leads to creating 16MB log segment files every 5
minutes (default checkpoint period), which will in turn
Benny Amorsen wrote:
TL == Tom Lane [EMAIL PROTECTED] writes:
TL (I suppose it wouldn't work in Windows for lack of hard links, but
TL anyone trying to run a terabyte database on Windows deserves to
TL lose anyway.)
Windows has hard links on NTFS, they are just rarely used.
Magnus Hagander [EMAIL PROTECTED] writes:
I've posted a 6.5kB patch (as an attachment) three times over the
past few days but haven't seen it hit the lists. Checking to see if
this goes through.
Did you by any chance gzip it? IIRC, mails with gzipped attachments are
silently dropped on-
Tom Lane wrote:
Magnus Hagander [EMAIL PROTECTED] writes:
I've posted a 6.5kB patch (as an attachment) three times over the
past few days but haven't seen it hit the lists. Checking to see if
this goes through.
Did you by any chance gzip it? IIRC, mails with gzipped attachments are
I've posted a 6.5kB patch (as an attachment) three times over
the
past few days but haven't seen it hit the lists. Checking to see
if
this goes through.
Did you by any chance gzip it? IIRC, mails with gzipped
attachments
are silently dropped on- patches for some reason.
Hm?
For 8.3, I'd like to add the following two related features to assist
with Index Tuning and usability:
- Virtual Indexes
An index which only exists in the catalog, so is visible to the planner
but not the executor. This is useful where a specific SQL query is being
hand-tuned, allowing very
Simon Riggs wrote:
For 8.3, I'd like to add the following two related features to assist
with Index Tuning and usability:
- Virtual Indexes
This seems useful, but I'm not sure we need a catalog object for that.
It might be sufficient to declare these hypothetical indexes within the
EXPLAIN
Simon Riggs [EMAIL PROTECTED] writes:
- Virtual Indexes
An index which only exists in the catalog, so is visible to the planner
but not the executor.
Say what? What would that possibly be useful for, other than crashing
any bit of code that failed to know about it?
- RECOMMEND command
Peter Eisentraut wrote:
Simon Riggs wrote:
For 8.3, I'd like to add the following two related features to assist
with Index Tuning and usability:
- Virtual Indexes
This seems useful, but I'm not sure we need a catalog object for that.
It might be sufficient to declare these hypothetical
Luke Lonergan wrote:
+1
Mark, can you quantify the impact of not running with IRQ balancing enabled?
Whoops, look like performance was due more to enabling the
--enable-thread-safe flag.
IRQ balancing on : 7086.75
http://dbt.osdl.org/dbt/dbt2dev/results/dev4-015/158/
IRQ balancing
One of our customers noticed that there were a high number of NUMA cache
misses on a quad core opteron system running Bizgres MPP resulting in about
a 15% performance hit. We use a process-based parallelization approach and
we can guess that there's context switching due to the high degree of
On Tue, 2006-10-10 at 22:26 +0900, Tatsuo Ishii wrote:
If archive_timeout is set to non 0, it seems an archive log segment is
created every time checkpoint occurs even there's no database
updation. This leads to creating 16MB log segment files every 5
minutes (default checkpoint period), which
Jeff Davis [EMAIL PROTECTED] writes:
There should be a documentation note to let people know that the archive
will grow even when idle. Perhaps we should suggest compression in the
docs so that people don't get worried about many gigabytes of mostly-
empty files filling up their backup
Yeah, I'm sure binding each process to a CPU would be a significant
help. Something I've always wanted to quantify but haven't made time for...
Mark
Luke Lonergan wrote:
One of our customers noticed that there were a high number of NUMA cache
misses on a quad core opteron system running
On Tue, 2006-10-10 at 13:12 -0400, Tom Lane wrote:
Jeff Davis [EMAIL PROTECTED] writes:
There should be a documentation note to let people know that the archive
will grow even when idle. Perhaps we should suggest compression in the
docs so that people don't get worried about many gigabytes
Jeff Davis [EMAIL PROTECTED] writes:
Maybe I just don't understand checkpoint timeout? Could it reasonably be
set to something like 12 hours? I can't think why not, but the config
default is 5 minutes, so I would be hesitant to change it by that much.
The only constraining factor on it is how
On Tue, Oct 10, 2006 at 06:06:09PM +0200, Peter Eisentraut wrote:
Simon Riggs wrote:
For 8.3, I'd like to add the following two related features to assist
with Index Tuning and usability:
- Virtual Indexes
This seems useful, but I'm not sure we need a catalog object for that.
It
... as an example, I see you removed material from 8.1's FAQ_HPUX that
is still relevant to that branch.
regards, tom lane
---(end of broadcast)---
TIP 3: Have you checked our extensive FAQ?
[EMAIL PROTECTED] ~/postgresql-8.2beta1]$ ./configure --enable-debug
--with-cassert
checking build system type... i386-pc-solaris2.10
checking host system type... i386-pc-solaris2.10
checking which template to use... solaris
checking whether to build with 64-bit integer date/time support... no
Joseph Shraibman wrote:
[EMAIL PROTECTED] ~/postgresql-8.2beta1]$ ./configure --enable-debug
--with-cassert
configure: error: readline library not found
If you have readline already installed, see config.log for details on the
failure. It is possible the compiler isn't looking in the proper
Tom Lane wrote:
... as an example, I see you removed material from 8.1's FAQ_HPUX that
is still relevant to that branch.
Are we trimming platform-specific FAQs as we move forward? I figured an
FAQ just got more accurate. And I only backpatch to the most recent
branch.
Are you talking about
Use --without-readline to disable readline support.
[EMAIL PROTECTED] ~/postgresql-8.2beta1]$ uname -a
SunOS xx 5.10 Generic i86pc i386 i86pc
Do you have readline installed?
It's not standard on Solaris. I don't know if it's even available from
Blastwave.
--
--Josh
Josh Berkus
Joshua D. Drake wrote:
Joseph Shraibman wrote:
[EMAIL PROTECTED] ~/postgresql-8.2beta1]$ ./configure --enable-debug
--with-cassert
configure: error: readline library not found
If you have readline already installed, see config.log for details on the
failure. It is possible the compiler isn't
Josh Berkus wrote:
Use --without-readline to disable readline support.
[EMAIL PROTECTED] ~/postgresql-8.2beta1]$ uname -a
SunOS xx 5.10 Generic i86pc i386 i86pc
Do you have readline installed?
It's not standard on Solaris. I don't know if it's even available from
Blastwave.
Apparently
Joseph S wrote:
Joshua D. Drake wrote:
Joseph Shraibman wrote:
[EMAIL PROTECTED] ~/postgresql-8.2beta1]$ ./configure --enable-debug
--with-cassert
configure: error: readline library not found
If you have readline already installed, see config.log for details
on the
failure. It is possible
Joseph S jks@selectacast.net writes:
Anyway I installed the readline package from blastwave but the configure
script still didn't find it.
Where does blastwave put it? You likely need --with-includes and/or
--with=libraries switches to tell configure where to look.
Tom Lane wrote:
Joseph S jks@selectacast.net writes:
Anyway I installed the readline package from blastwave but the configure
script still didn't find it.
Where does blastwave put it? You likely need --with-includes and/or
--with=libraries switches to tell configure where to look.
Joseph S wrote:
Josh Berkus wrote:
Use --without-readline to disable readline support.
[EMAIL PROTECTED] ~/postgresql-8.2beta1]$ uname -a
SunOS xx 5.10 Generic i86pc i386 i86pc
Do you have readline installed?
It's not standard on Solaris. I don't know if it's even available
from
Zdenek Kotala wrote:
+ The PostgreSQL 8.2 has implemented dtrace support. You can enable it by
+ the --enable-dtrace configure switch. If you want to compile a 64-bit code
+ with dtrace you must specify DTRACEFLAGS='-64', e.g.
This is contrary to the documentation of the dtrace command which
Joseph S wrote:
Tom Lane wrote:
Joseph S jks@selectacast.net writes:
Anyway I installed the readline package from blastwave but the
configure script still didn't find it.
Where does blastwave put it? You likely need --with-includes and/or
--with=libraries switches to tell configure where
Joseph,
How about just compiling --without-readline?
Also, if you have Sun Studio 11 available, you'll get better performance
out of your PostgreSQL.
--
--Josh
Josh Berkus
PostgreSQL @ Sun
San Francisco
---(end of broadcast)---
TIP 6: explain
Andrew Dunstan [EMAIL PROTECTED] writes:
Joseph S wrote:
checking test program... failed
configure: error:
*** Could not execute a simple test program. This may be a problem
*** related to locating shared libraries. Check the file 'config.log'
*** for the exact reason.
I had similar
Hi,
While returning from a function call, PL can easily interfere will be
returned HeapTuple's TupleDesc from fcinfo. But what if function returns
a record type? Then we must create our own TupleDesc (or AttInMetadata)
for the related attribute (and then create HeapTuple). So far everything
is
Joseph S jks@selectacast.net writes:
I'm attaching the whole log.
It appears that blastwave's version of readline passes the link test:
configure:6320: checking for -lreadline
configure:6347: gcc -o conftest -O2 -Wall -Wmissing-prototypes
-Wpointer-arith -Winline
On Tuesday 10 October 2006 12:06, Tom Lane wrote:
Similar in usage to an EXPLAIN, the RECOMMEND command would return a
list of indexes that need to be added to get the cheapest plan for a
particular query (no explain plan result though).
Both of these seem to assume that EXPLAIN results,
Greg Sabino Mullane [EMAIL PROTECTED] writes:
Sure, but the question is whether that incremental gain in capability
is worth the extra logical complexity. I'm inclined to think that many
more users would get burned by the complexity than would have use for
it.
I disagree - we lose a lot of
Tom Lane wrote:
This most likely means that libreadline depends on another shared
library (termcap maybe?) that isn't installed in your default search
path; so you'd need to set LD_LIBRARY_PATH or LD_RUN_PATH --- see
item 3 in our FAQ_Solaris for info. One would think that blastwave's
Neil Conway [EMAIL PROTECTED] writes:
BTW, I think it would make sense to implement a limited subset of the
xfunc ideas: add options to CREATE FUNCTION to allow cost information to
be specified, and then take advantage of this information instead of
using the existing constant kludges. This
Robert Treat [EMAIL PROTECTED] writes:
Anything that can be done to wheedle down your choices
before you have to run EXPLAIN ANALYZE is a bonus.
Fair enough, but I prefer Peter's suggestion of attaching the
hypothetical index definitions to EXPLAIN itself, rather than making
bogus catalog
Simon Riggs [EMAIL PROTECTED] writes:
- RECOMMEND command
Similar in usage to an EXPLAIN, the RECOMMEND command would return a
list of indexes that need to be added to get the cheapest plan for a
particular query (no explain plan result though).
Both of these seem to assume that EXPLAIN
IIRC there was an intention to allow ownership reassignment of all
objects in the database. Somehow views got missed (probably because they
don't currently have an ALTER command). If there isn't a lot of code
involved in making this happen, I'd argue it should go in as a bug fix.
If not, can we
On Tue, 2006-10-10 at 20:17 -0500, Jim C. Nasby wrote:
IIRC there was an intention to allow ownership reassignment of all
objects in the database. Somehow views got missed
ALTER TABLE can change view ownership (as well as sequence ownership).
You could argue for the addition of an ALTER VIEW
On Tue, Oct 10, 2006 at 09:23:34PM -0400, Neil Conway wrote:
On Tue, 2006-10-10 at 20:17 -0500, Jim C. Nasby wrote:
IIRC there was an intention to allow ownership reassignment of all
objects in the database. Somehow views got missed
ALTER TABLE can change view ownership (as well as
On Tue, 2006-10-10 at 20:27 -0500, Jim C. Nasby wrote:
Wow, that's news to me. I'll prepare a docs patch to reflect that.
It is already reflected in the docs, although it might need to be more
prominent.
Is there any other operations ALTER TABLE can perform on a view?
IIRC, it can be used to
On Tue, Oct 10, 2006 at 09:33:13PM -0400, Neil Conway wrote:
On Tue, 2006-10-10 at 20:27 -0500, Jim C. Nasby wrote:
Wow, that's news to me. I'll prepare a docs patch to reflect that.
It is already reflected in the docs, although it might need to be more
prominent.
Yeah, it should be listed
Mark,
Another thing that this brings up is hints to a query. Over the years,
I have run into situation where the planner wasn't great. It would be
nice to try forcing different strategies on the planner and see if
performance caan be improved.
See discussion on -performance.
--
--Josh
On 10/10/06, Mark Woodward [EMAIL PROTECTED] wrote:
I think the idea of virtual indexes is pretty interesting, but
ultimately a lesser solution to a more fundimental issue, and that would
be hands on control over the planner. Estimating the effect of an index
on a query prior to creating the
57 matches
Mail list logo