hrashing that badly, you need more RAM and/or more
spindles; using an index will just put even more load on the i/o
system.
-Doug
--
Doug McNaught Wireboard Industries http://www.wireboard.com/
Custom software development, systems and network consulting.
Java PostgreSQL
License. The GPL is offering multiple advantages for a big project and
> software like PostgreSQL. For example :
Not open for discussion. See the FAQ.
-Doug
--
Doug McNaught Wireboard Industries http://www.wireboard.com/
Custom software development, systems and network consulti
Shad <[EMAIL PROTECTED]> writes:
> I just recently upgraded from 7.0.x to 7.2.1. I installed from
> postgresql-7.2.1-2PGDG.i386.rpm on a Linux Redhat 7.1 system. I was
> able to resolve most dependancies, except for it telling me that I
> needed libreadline.so.4, which " ldconfig -p|grep readli
"Marc G. Fournier" <[EMAIL PROTECTED]> writes:
> Just as a stupid question here ... but, why do we wrap single queries into
> a transaction anyway? IMHO, a transaction is meant to tell the backend to
> remember this sequence of events, so that if it fails, you can roll it
> back ... with a singl
"John Liu" <[EMAIL PROTECTED]> writes:
> I tried to understand what causes
> too many pgsql idle processes. Can
> postmaster automatically aged and
> cleaning up those unused idle process?
Those processes are attached to open client connections. If you don't
like them, change your client to clo
Bruce Momjian <[EMAIL PROTECTED]> writes:
> Can anyone clarify if "data=writeback" is safe for PostgreSQL.
> Specifically, are the data files recovered properly or is this option
> only for a filesystem containing WAL?
"data=writeback" means that no data is journaled, just metadata (which
is li
Tom Lane <[EMAIL PROTECTED]> writes:
> We'd be happiest with a filesystem that journals its own metadata and
> not the user data in the file(s). I dunno if there are any.
ext3 with data=writeback? (See my previous message to Bruce).
-Doug
---(end of broadcast)
Bruce Momjian <[EMAIL PROTECTED]> writes:
> Doug McNaught wrote:
> > Tom Lane <[EMAIL PROTECTED]> writes:
> >
> > > We'd be happiest with a filesystem that journals its own metadata and
> > > not the user data in the file(s). I dunno if there
Tom Lane <[EMAIL PROTECTED]> writes:
> "Curtis Faith" <[EMAIL PROTECTED]> writes:
> > The log file would be opened O_DSYNC, O_APPEND every time.
>
> Keep in mind that we support platforms without O_DSYNC. I am not
> sure whether there are any that don't have O_SYNC either, but I am
> fairly su
Tom Lane <[EMAIL PROTECTED]> writes:
> In practice I am not sure there is a problem. The local man page for
> sync() says
>
> The writing, although scheduled, is not necessarily complete upon
> return from sync.
>
> Now if "scheduled" means "will occur before any subsequently-command
Tom Lane <[EMAIL PROTECTED]> writes:
> Doug McNaught <[EMAIL PROTECTED]> writes:
> > In my understanding, it means "all currently dirty blocks in the file
> > cache are queued to the disk driver". The queued writes will
> > eventually complete, bu
"D. Hageman" <[EMAIL PROTECTED]> writes:
> This in many ways is a bogus argument in that 1) postgresql runs on more
> then just Linux and 2) amount of memmory that can be addressed by a
> process is tunable up to the point that it reaches a hardware limitation.
1) The OP specifically asked abou
Tom Lane <[EMAIL PROTECTED]> writes:
> Bruce Momjian <[EMAIL PROTECTED]> writes:
> > Folks. start sending in those plaform reports, OS name and version
> > number please.
>
> I've checked CVS tip on:
> HPUX 10.20, using both gcc and vendor's cc
> PPC Linux
> Mac OS X 10.1
I get
Tom Lane <[EMAIL PROTECTED]> writes:
> Doug McNaught <[EMAIL PROTECTED]> writes:
> > make[3]: Entering directory
>`/home/doug/src/pgsql/src/backend/utils/mb/conversion_procs/ascii_and_mic'
> > gcc -O2 -Wall -Wmissing-prototypes -Wmissing-declarations -fpic
"Steve Wolfe" <[EMAIL PROTECTED]> writes:
> On the recurring debate of threading vs. forking, I was giving it a fwe
> thoughts a few days ago, particularly with concern to Linux's memory model.
>
> On IA32 platforms with over 4 gigs of memory, any one process can only
> "see" up to 3 or 4 gig
Joe Conway <[EMAIL PROTECTED]> writes:
> Tom Lane wrote:
> > A depth limit for PL-function recursion is perhaps feasible, but I can't
> > say that I care for it a whole lot ... anyone have better ideas?
> >
>
> Is there any way to recognize infinite recursion by analyzing the
> saved execution tr
Doug McNaught <[EMAIL PROTECTED]> writes:
> OK, compile went fine, but I get multiple regression test failures:
>
> test geometry ... FAILED
After realizing that my disk had filled up (thanks Alvaro) I reran the
tests and 'geometry' is the only failure. I&
Barry Lind <[EMAIL PROTECTED]> writes:
> If we had to supply gcj along with PostgreSQL in order for PostgreSQL to
> work, I guess that would mean gcj was incorporated in PostgreSQL - that
> would mean PostgreSQL would become subject to GPL protection.
Not true--"mere aggregation" (shipping two th
Philip Warner <[EMAIL PROTECTED]> writes:
> At 07:39 PM 2/11/2002 +1100, Philip Warner wrote:
> The latter time is actually quote good; when the machine is more
> heavily loaded it goes up to 1ms.
>
> We currently vacuum/analyze daily, and analyze hourly.
Why not vacuum hourly (regular non-
Christopher Kings-Lynne <[EMAIL PROTECTED]> writes:
> chriskl@alpha:~/pgsql-head$ bison --version
> GNU Bison version 1.28
Upgrade Bison to 1.50 or later. Earlier versions can't handle the
size of the current grammar.
-Doug
---(end of broadcast)-
Oleg Bartunov <[EMAIL PROTECTED]> writes:
> May be I miss something, but seems there is a problem with float4
> in 7.2.3 and 7.3RC1 (6.53 works fine):
>
> test=# create table t ( a float4);
> CREATE TABLE
> test=# insert into t values (0.1);
> INSERT 32789 1
> test=# select * from t where a=0.1;
Lee Kindness <[EMAIL PROTECTED]> writes:
> Tom Lane writes:
> > Okay, so it seems -D_REENTRANT is the appropriate fix.
> >
> > We could either add that to the template/solaris file, or just add a
> > note to FAQ_Solaris advising that it be added to the configure switches
> > if people intend
Justin Clift <[EMAIL PROTECTED]> writes:
> OS/400 is the operating system on the IBM AS/400 series of midrange
> computers:
>
> Info:
> http://search400.techtarget.com/sDefinition/0,,sid3_gci331973,00.html
>
> IBM AS/400 page:
> http://www-132.ibm.com/content/home/store_IBMPublicUSA/en_US/eServe
"Dann Corbit" <[EMAIL PROTECTED]> writes:
> No analyze for 7.1.3.
> Just ran vacuum a few minutes before the query. No boost at all.
VACUUM or VACUUM ANALYZE? Standalone ANALYZE was not in 7.1 but
VACUUM ANALYZE does what you need to do...
-Doug
---(end of broadcast)-
It's all over Slashdot:
http://security.e-matters.de/advisories/012003.html
-Doug
---(end of broadcast)---
TIP 2: you can get off all lists at once with the unregister command
(send "unregister YourEmailAddressHere" to [EMAIL PROTECTED])
"Homayoun Yousefi'zadeh" <[EMAIL PROTECTED]> writes:
> I did what you suggested and nothing changed.
> Actually, JDBC problem seems to be ant related
> as it did not exist w/ version 7.0.3.
You might want to double-check that JAVAHOME (sp?) is set before you
make. I had problems building with A
"Homayoun Yousefi'zadeh" <[EMAIL PROTECTED]> writes:
> Thanks for the response. I actually went thru
> the full exercise when I was compiling Tomcat
> engine with Ant. Every thing seems to be set up
> properly. This is a part od /etc/profile file
> that shows the settings of environmental variabl
Tom Lane <[EMAIL PROTECTED]> writes:
> > Rather than do system('uptime') and incur the process start-up each time,
> > you could do fp = popen('vmstat 60', 'r'), then just read the fp.
>
> popen doesn't incur a process start? Get real. But you're right, popen()
> is the right call not system()
[EMAIL PROTECTED] (Robert E. Bruccoleri) writes:
> I have been using PostgreSQL and XFS file systems on SGI's for many
> years, and PostgreSQL is fast. Dumping and loading 100GB of table
> files takes less than one day elapsed (provided there is no other
> activity on that database -- large amoun
Bruce Momjian <[EMAIL PROTECTED]> writes:
> Yes, the irony is that a journaling file system is being used to have
> fast, reliable restore after crash bootup, but with no fsync, the db is
> probably hosed.
It just struck me--is it necessarily true that we get the big
performance hit?
On a non
"P. Dwayne Miller" <[EMAIL PROTECTED]> writes:
> What's the fastest way to select the number of rows in a table? If I
> use count(*) with no whereclause, it uses a seq_scan and takes 4 secs
> (122k rows). With a where clause, it uses an index and returns in < 1
> sec. Selecting count(requestnu
"August Zajonc" <[EMAIL PROTECTED]> writes:
> Curious if anyone has done any work on client side connection pooling
> recently? I'm thinking pooling multiplexed against transaction commits?
^^^
What does this phrase mean exactl
"August Zajonc" <[EMAIL PROTECTED]> writes:
> One possible pooling model is to have a bunch of worker connections opened
> to the pgsql instance. Then as sql statements arrive the they are routed
> through an available connection that is open but not doing any work. So 100
> inbound connection ma
mlw <[EMAIL PROTECTED]> writes:
> Somehow I guess I created a misunderstanding. I don't really care about
> ROWID. I care that OID is a 32 bit number. The notion that each table could
> have its own "OID" similar to a ROWID could be an intermediate solution. I
> have flip-flopped a couple times a
"gabriel" <[EMAIL PROTECTED]> writes:
> hello all
>
> I have a perl script that read a text file and
> insert the data in a table...
>
> but when this script is runing the usage of CPU by postmaster grows to
> between 79 and 90 percent...
And this is a problem because... ?
Honestly, you're
Bruce Momjian <[EMAIL PROTECTED]> writes:
> Look at this from the BSD/OS crypt() manual page:
>
> The crypt function performs password encryption. It is derived from the
> NBS Data Encryption Standard. Additional code has been added to deter
> key search attempts. The first arg
Bruce Momjian <[EMAIL PROTECTED]> writes:
> > > and conn.salt is char[2]. Isn't this a problem?
> >
> > I don't think it is. Note that it refers to the salt as a "character
> > array", not a string. Also, since '_' isn't in the allowed encoding
> > set, it can tell the difference between a 9-
Peter Moscatt <[EMAIL PROTECTED]> writes:
> Thanks Tony... yes that helps explain why I am not seeing what I expected
> to see.
>
> Right. If I was developing an application, say with Python and I
> needed to transport my created database and make it part of an installation
> process (cr
Peter Moscatt <[EMAIL PROTECTED]> writes:
> I am pretty new to PostgreSQL so please bare with me :-)
>
> When issuing the CREATEDB MyDb then creating some tables with CREATE
> TABLE, I then go back and do a search for the file I have just created
> (MyDb) but can't find the physical file.
>
"Christopher Kings-Lynne" <[EMAIL PROTECTED]> writes:
> Are you sure? I thought all that autocommit meant was that a statement that
> is not enclosed within a begin/commit is automatically committed after it is
> run. So, in the this case all three queries will be independent, unless the
> firs
"Joe Conway" <[EMAIL PROTECTED]> writes:
> > Having said that, I'm not married to the idea that we should provide
> access
> > to both /dev/random and /dev/urandom. I'd be happy to roll another patch,
> > limited to just urandom, and renaming the function if you feel strongly
> > about it. (shoul
Mike Cianflone <[EMAIL PROTECTED]> writes:
> Is there a problem with running vacuum, or vacuum analyze in the
> middle of making transactions? If there happens to be a transaction running
> at the time I do a vacuum analyze, the transaction has problems and the
> trigger doesn't get complet
Tom Lane <[EMAIL PROTECTED]> writes:
> Doug McNaught <[EMAIL PROTECTED]> writes:
> > Hmmm--AFAIK, VACUUM is supposed to grab locks on the tables it
> > processes, which will block until all open transactions against that
> > table are finished. So either VACU
"D. Hageman" <[EMAIL PROTECTED]> writes:
> Save for the fact that the kernel can switch between threads faster then
> it can switch processes considering threads share the same address space,
> stack, code, etc. If need be sharing the data between threads is much
> easier then sharing between
Gavin Sherry <[EMAIL PROTECTED]> writes:
> This aside, isn't it possible to just copy the socket and some
> data about the database required into shared memory and have the preforked
> children pick the socket up from there.
Ummm No. There's no Unix API for doing so.
You can pass open fil
"Jason Orendorff" <[EMAIL PROTECTED]> writes:
> Reply-To: sender
Just to be nice, I'll do this. ;)
> Hi. I was surprised to discover today that postgres's
> character types don't support zero bytes. That is,
> Postgres isn't 8-bit clean. Why is that?
As I understand it, the storage system i
Reiner Dassing <[EMAIL PROTECTED]> writes:
> Hello PostgreSQl Users!
>
> PostSQL V 7.1.1:
>
> I have defined a table and the necessary indices.
> But the index is not used in every SELECT. (Therefore, the selects are
> *very* slow, due to seq scan on
> 20 million entries, which is a test setup
David Ford <[EMAIL PROTECTED]> writes:
> I've got a bit of a problem. I added a fast SIGALRM handler in my project to
> do various maintenance and this broke PQconnectStart().
>
>
> Oct 23 21:56:36 james BlueList: connectDBStart() -- connect() failed:
> Interrupted system call ^IIs the postmas
Well, O_DIRECT has finally made it into the Linux kernel. It lets you
open a file in such a way that reads and writes don't go to the buffer
cache but straight to the disk. Accesses must be aligned on
filesystem block boundaries.
Is there any case where PG would benefit from this? I can see
"D. Hageman" <[EMAIL PROTECTED]> writes:
> The plan for the new spinlocks does look like it has some potential. My
> only comment in regards to permformance when we start looking at SMP
> machines is ... it is my belief that getting a true threaded backend may
> be the only way to get the ful
g, which enables
> TCP/IP networking.
Is the postmaster indeed listening on a TCP/IP port, (usually 5432) or
just on the Unix-domain socket? You have to specifically turn on
TCP/IP for security reasons--it's not enabled by default.
-Doug
--
Doug McNaught Wireboard Industries http:/
re developers would certainly be willing to look at such a
design proposal. Then, if they like it, you get to implement it. ;)
In other words, and I say this in the nicest possible way, talk is
cheap.
-Doug
--
Doug McNaught Wireboard Industries http://www.wireboard.com/
C
ironment (PG runs on Windows, but only through a
Unix emulation layer--I personally wouldn't run it in production,
but then again I wouldn't run Windows in production:)
Both offer commercial support, ACID compliance, stored
procedures/functions, and the other stuff that people expect f
r running (whether it's your JVM, Apache process for
mod_perl or PHP, or whatever). Really big apps definitely have a
long-running daemon process that handles caching, session management
(so you can have multiple webservers) etc etc...
-Doug
--
Doug McNaught Wireboard Industr
ort (greater than 2GB).
Is this on Linux?
-Doug
--
Doug McNaught Wireboard Industries http://www.wireboard.com/
Custom software development, systems and network consulting.
Java PostgreSQL Enhydra Python Zope Perl Apache Linux BSD...
---(end of broadc
to do to "turn on large file support" in the compile?
Make sure you are running the latest kernel and libs, and AFAIK
'configure' should set it up for you automatically.
-Doug
--
Doug McNaught Wireboard Industries http://www.wireboard.com/
Custom software
problem?
Might be. Make sure you have up to date kernel and libs on the
compile machine and the one you're running on. Make sure your
filesystem supports files greater than 2GB.
Also, if you are using shell redirection to create the output file,
it's possible the shell isn't usin
cygwin. Thanks -Dean
Minor upgrades do not require a dump/restore; the on-disk file format
remains the same.
-Doug
--
Doug McNaught Wireboard Industries http://www.wireboard.com/
Custom software development, systems and network consulting.
Java PostgreSQL Enh
vailable,
> anywhere, and always use that version on all platforms?
Because qsort() is *supposed* to be optimized by the vendor for their
platform, perhaps even written in assembler. It makes sense to trust
the vendor except when their implementation is provably pessimized.
-Doug
--
Doug McNaugh
o be a fast in-memory sort.
The qsort() name is just a historical artifact.
-Doug
--
Doug McNaught Wireboard Industries http://www.wireboard.com/
Custom software development, systems and network consulting.
Java PostgreSQL Enhydra Python Zope Perl Apache Linux
peed. By storing the current number and incrementing for
> every insert and decrementing for every delete, the count(*) case with
> no where clause can return the value instantly.
How would this work with MVCC?
-Doug
--
Doug McNaught Wireboard Industries http://www.wireboard.com/
er things) that Postgresql cannot be used for a data warehouse.
Have you read the doc chapter about MVCC? Sounds like you don't
quite understand how it works yet.
-Doug
--
Doug McNaught Wireboard Industries http://www.wireboard.com/
Custom software development, syst
the count(*) reflecting INSERTs in
your transaction, but others won't until you commit. So there is no
well-defined concept of cardinality under MVCC--it depends on which
rows are visible to which transactions.
-Doug
--
Doug McNaught Wireboard Industries http://www.wireboar
Tom Lane <[EMAIL PROTECTED]> writes:
> "Mikheev, Vadim" <[EMAIL PROTECTED]> writes:
> >> The idea is, that by the time the last sync has run, the
> >> first sync will be done flushing the buffers to disk. - this is what
> >> we were told by the IBM engineers when I worked tier-2/3 AIX support
>
Just a quick delurk to pass along this tidbit from linux-kernel on
Linux *sync() behavior, since we've been talking about it a lot...
-Doug
Hi,
On Wed, Mar 14, 2001 at 10:26:42PM -0500, Tom Vier wrote:
> fdatasync() is the same as fsync(), in linux.
No, in 2.4 fdatasync does the right thing
Tom Lane <[EMAIL PROTECTED]> writes:
> Doug McNaught <[EMAIL PROTECTED]> forwards:
> >> 2.4's O_SYNC actually does a fdatasync internally. This is also the
> >> default behaviour of HPUX, which requires you to set a sysctl variable
> >> if you
Tom Lane <[EMAIL PROTECTED]> writes:
> Alfred Perlstein <[EMAIL PROTECTED]> writes:
> >> definitely need before considering this is to replace the existing
> >> spinlock mechanism with something more efficient.
>
> > What sort of problems are you seeing with the spinlock code?
>
> It's great as
Tom Lane <[EMAIL PROTECTED]> writes:
> Alexander Klimov <[EMAIL PROTECTED]> writes:
> > Suddenly I obtain access to
> > ULTRIX black 4.3 1 RISC
>
> Uh ... what kind of processor is that? Offhand I don't see any
> indication that any of the entries in s_lock.h are supposed to work
> for Ultrix.
Neil Conway <[EMAIL PROTECTED]> writes:
> About 1 in every 5 runs of the (parallel) regression tests are failing
> for me with CVS HEAD: the triggers, inherit, vacuum, sanity_check, and
> misc tests fail. I can make the failures occur fairly consistently by
> running "make check" over and over aga
"Christopher Kings-Lynne" <[EMAIL PROTECTED]> writes:
> I'd be in favour of creating whole sets of backwards-compatibility GUC's
> whenever we break backwards compatibility.
>
> eg.
> use_72_compat = yes
> use_73_compat = yes
That sounds like a recipe for a maintenance nightmare to me.
-Doug
-
Bruce Momjian <[EMAIL PROTECTED]> writes:
> Tom Lane wrote:
> > AFAIK the only good way around this problem is to use another OS with a
> > more rational design for handling low-memory situations. No other Unix
> > does anything remotely as brain-dead as what Linux does. Or bug your
> > favorite
Adam Haberlach <[EMAIL PROTECTED]> writes:
> So, one of the many machines that I support seems to have developed
> an incredibly odd and specific corruption that I've never seen before.
>
> Whenever a query requiring an aggregate is attempted, it spits out:
> cannot open pg_aggregate: No su
"Shridhar Daithankar" <[EMAIL PROTECTED]> writes:
> Hi,
>
> I was just wondering over it. This is for difference between vacuum full and
> vacuum analyze. Can somebody enlighten,
>
> 1. IIRC vacuum recovers/reuses dead tuples generated from update but can not do
> so for delete? Why?
YDNRC.
"Serguei A. Mokhov" <[EMAIL PROTECTED]> writes:
> On Wed, 3 Sep 2003, Alvaro Herrera wrote:
>
> > On Wed, Sep 03, 2003 at 09:19:33PM -0400, Serguei A. Mokhov wrote:
> > > On the contrary, it could show the transaction level for the case of
> > > nested transactions:
> > >
> > > foo**=#
> >
>
"Dann Corbit" <[EMAIL PROTECTED]> writes:
> Cygwin requires a license for commercial use.
"Use" in the sense of distributing applications linked against it,
yes.
In this case I don't think it's a problem. The output of 'flex' and
'bison' is not required to be GPL (there is a specific exception
Andreas Pflug <[EMAIL PROTECTED]> writes:
> Tom Lane wrote:
>
> >
> >2. Throw an error if the expression doesn't return boolean.
> >
> I'd opt for 2.
> It's quite common that newer compilers will detect more bogus coding
> than older ones. There might be existing functions that break from
> this
Tom Lane <[EMAIL PROTECTED]> writes:
> Doug McNaught <[EMAIL PROTECTED]> writes:
> > I agree with another poster that deprecation in 7.4 and removal in
> > 7.5 might make sense.
>
> How would we "deprecate" it exactly? Throw a NOTICE?
I was thinking
ivan <[EMAIL PROTECTED]> writes:
> hi,
>
> ist possible to compile postgres (after same small modification) to shared
> so, or dll , and usr it like normal postgres , but without any server and
> so on.
Not without very major code changes.
-Doug
---(end of broadcast)---
Jon Jensen <[EMAIL PROTECTED]> writes:
> On Wed, 10 Sep 2003, Alvaro Herrera wrote:
>
> > On Wed, Sep 10, 2003 at 10:35:18PM +0200, Andreas Pflug wrote:
> >
> > > I never agreed that a client solution would be satisfying. While
> > > frontends might try to hide some uglyness of the syntax to th
Robert Treat <[EMAIL PROTECTED]> writes:
> If by "stripped down" you mean without postgresql database support then
> I'll grant you that, but it is no different than other any other pl
> whose parent language requires postgresql to be installed. If packagers
> are able to handle those languages t
Tom Lane <[EMAIL PROTECTED]> writes:
> "Dave Held" <[EMAIL PROTECTED]> writes:
>> How about an optional second connection to send keepalive pings?
>> It could be unencrypted and non-blocking. If authentication is
>> needed on the ping port (which it doesn't seem like it would need
>> to be), it c
[EMAIL PROTECTED] (James Thornton) writes:
> I want to understand how Postgres organizes data and handles IO
> operations so that I will better know how to optimize a Postgres
> database server. I am looking for answers to specific questions and
> pointers to where this stuff is documented.
If yo
Greg Stark <[EMAIL PROTECTED]> writes:
> Marko Karppinen <[EMAIL PROTECTED]> writes:
>
>> On 17. touko 2004, at 10:40, Tatsuo Ishii wrote:
>> > Consider a program using JDBC on localhost. It can only reach to
>> > PostgreSQL via TCP/IP.
>
> Huh? Why on earth would that be true? Is this a limitatio
Greg Stark <[EMAIL PROTECTED]> writes:
> Doug McNaught <[EMAIL PROTECTED]> writes:
>
>> Java doesn't support Unix domain sockets. If you want to use JDBC,
>> you have to use TCP sockets.
>
> That doesn't follow. That just means you can't impl
"Magnus Hagander" <[EMAIL PROTECTED]> writes:
>>> I would like to add capability to initdb to accept the
>>password for the
>>> superuser account at invocation. Right now, I can use
>>--pwprompt or -W
>>> to have it ask for a password. But for the win32 GUI
>>installed I'd like
>>> to ask for t
"Cason, Kenny" <[EMAIL PROTECTED]> writes:
> I'm having trouble accessing specific schemas and wonder if maybe I
> haven't installed something properly in 7.4.2. Here is what is
> happening:
>
> SELECT * FROM INFORMATION_SCHEMA.SCHEMATA;
>
> ERROR: parser: parse error at or near "."
>
> This erro
Christopher Browne <[EMAIL PROTECTED]> writes:
> Centuries ago, Nostradamus foresaw when [EMAIL PROTECTED] (Jaime Casanova) would
> write:
>> Can anyone tell me if postgresql has problems with xeon processors?
>>
>> If so, there is any fix or project of fix it?
>
> Well, there's a known issue tha
"Jonah H. Harris" <[EMAIL PROTECTED]> writes:
> this leads me to the first question I asked... do you want me to pull
> the latest cvs and patch it... or distribute my patch for 7.4.3?
Latest CVS, no question. It would be going into 7.6 (or whatever) T
the earliest...
-Doug
---
Tom Lane <[EMAIL PROTECTED]> writes:
> Huh? That is exactly counter to most people's expectations about
> version numbering. N.0 is the unstable release, N.1 is the one
> with some bugs shaken out. If we release a 7.5 people will expect
> it to be less buggy than 7.4, and I'm not sure we can pr
"Cason, Kenny" <[EMAIL PROTECTED]> writes:
> Is there an easy way to select, say, the 15th row in a table? I can't
> use a sequence number because rows will sometimes be deleted resulting
> in the 15th row now being a different row. I need to be able to select
> the 15th row regardless of whether
Mike G <[EMAIL PROTECTED]> writes:
> Hello,
>
> I will bring it up with the postgresql hackers.
>
> PS - Sorry for the new posting. I read these via digest.
Neither the Cygwin nor the (beta) Windows-native version of Postgresql
is supported in any way on Windows 9x/ME AFIAK. Anyone trying to ru
[EMAIL PROTECTED] writes:
>> Just out of interest, what happens to the difference if you use *ext3*
>> (perhaps with data=writeback)
>
> Actually, I was working for a client, so it wasn't a general exploritory,
> but I can say that early on we discovered that ext3 was about the worst
> file system
[EMAIL PROTECTED] writes:
> Something to think about:
>
> if you run PostgreSQL with fsync on, but you use the hardware write cache
> on your disk drives, how likely are you to lose data? Obviously, this is a
> fairly limited problem, as it only applies to power down (which you can
> control) or p
"Joshua D. Drake" <[EMAIL PROTECTED]> writes:
> >Yes, please. Please, please do not force all users to accept new
> > features in "stable" trees.
> What if the feature does break compatibility with old features?
> What if it is "truly" a new feature?
>
> One example would be that we are consider
Christopher Kings-Lynne <[EMAIL PROTECTED]> writes:
> FreeBSD 4.9 was released today. In the release notes was:
>
> 2.2.6 File Systems
>
> A new DIRECTIO kernel option enables support for read operations that
> bypass the buffer cache and put data directly into a userland
> buffer. This feature
"scott.marlowe" <[EMAIL PROTECTED]> writes:
> I would think the biggest savings could come from using directIO for
> vacuuming, so it doesn't cause the kernel to flush buffers.
>
> Would that be just as hard to implement?
Two words: "cache coherency".
-Doug
---(end o
"Marc G. Fournier" <[EMAIL PROTECTED]> writes:
> On Thu, 30 Oct 2003, David Fetter wrote:
>
> > Any chance of putting up a torrent for it? I'd be happy to host, but
> > I'd have to get the link on the downloads page somehow :)
>
> Put up a what ... ?
Google for "BitTorrent". It's a pretty dar
Shridhar Daithankar <[EMAIL PROTECTED]> writes:
> pg_dump can be selective but I don't think it can be incremental.
>
> I hope I got your point correctly.
I think he's really talking about PITR, which will not be in 7.4.
-Doug
---(end of broadcast)--
"Joshua D. Drake" <[EMAIL PROTECTED]> writes:
> Hello,
>
>Personally I am for long release cycles, at least for major releases.
> In fact
> as of 7.4 I think there should possibly be a slow down in releases with more
> incremental releases (minor releases) throughout the year.
That would pr
Tom Lane <[EMAIL PROTECTED]> writes:
> Peter Eisentraut <[EMAIL PROTECTED]> writes:
>
> > I wasn't aware that glib had this. I'll look.
>
> Of course the trouble with relying on glibc is that we'd have no solution
> for platforms that don't use glibc.
glib != glibc. glib is the low-level libr
1 - 100 of 134 matches
Mail list logo
