Bruce Momjian pgman@candle.pha.pa.us writes:
TABLE PERSISTENCE [ DROP | TRUNCATE | DEFAULT ]. Tables using
non-default logging should not use referential integrity with
default-logging tables.
I have to say this smells way too much like MySQL for me to feel
[EMAIL PROTECTED] writes:
1. Change memory context to TopMemoryContext and palloc everything there.
(However, I believe this still isn't shared between processes?)
Nope.
2. Use the shmem functions in src/backend/storage/ipc/shmem.c to create a
chunk of shared memory and use this (Although
Mark Woodward [EMAIL PROTECTED] writes:
The point is, that I have been working with this sort of use case for a
number of years, and being able to represent multiple physical databases
as one logical db server would make life easier. It was a brainstorm I had
while I was setting this sort of
Mark Woodward [EMAIL PROTECTED] writes:
It is similar to a proxy, yes, but that is just part of it. The setup and
running of these systems should all be managed.
All that requires is some scripts that wrap pg_ctl and bring the right
instances up and down, perhaps with a web interface on top of
Devrim GUNDUZ [EMAIL PROTECTED] writes:
http://pgfoundry.org/projects/pgnixinstaller/
We are actively looking for developers for the project. Please drop me
an e-mail if you want to join this project. We will use Python, so you
need to be a Python guy to join the project. We are in planning
Devrim GUNDUZ [EMAIL PROTECTED] writes:
On Mon, 2006-01-30 at 20:03 -0500, Doug McNaught wrote:
What value does this bring to systems that have a good package system
and up-to-date repositories? I can install Postgres today on Ubuntu
using a GUI tool, and install another GUI tool
Marc G. Fournier [EMAIL PROTECTED] writes:
On Tue, 31 Jan 2006, Devrim GUNDUZ wrote:
On my RHEL boxes, I do never ever recompile the kernel since Red Hat
does not provide support if I do so :)
Is everything 'loadable modules' then? I can't imagine you have some
mammoth kernel running on
Martijn van Oosterhout kleptog@svana.org writes:
I would vote for the kernel, if the server didn't respond within 5
seconds, to simply return EIO. At least we know how to handle that...
You can do this now by mounting 'soft' and setting the timeout
appropriately. Whether it's really the best
Doug Royer [EMAIL PROTECTED] writes:
From the Linux 'nfs' man page:
intr If an NFS file operation has a major timeout and it is
hard mounted, then allow signals to interupt the file
operation and cause it to return EINTR to the calling
Doug Royer [EMAIL PROTECTED] writes:
The MOUNT options are opposite.
Linux NFS mount - defualts to no-intr
Solaris NFS mount - default to intr
Oh, right--I didn't realize that was what you were talking about.
-Doug
---(end of broadcast)---
Doug Royer [EMAIL PROTECTED] writes:
Yes - if you assume that EINTR only happens on NFS mounts.
My point is that independent of NFS, the error checking
that I have found in the code is not complete even for
non-NFS file systems.
The read() and write() LINUX man pages do NOT specify that
Doug Royer [EMAIL PROTECTED] writes:
The 'intr' option to NFS is not the same as EINTR. It
it means 'if the server does not respond for a while,
then return an EINTR', just like any other disk read()
or write() does when it fails to reply.
No, you're thinking of 'soft'. 'intr' (which is
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 could be very
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 than why
John DeSoi [EMAIL PROTECTED] writes:
I'm communicating with psql via a pipe stream. This works pretty well,
but one problem I have is trying to cancel an operation. If I send a
sigint, psql dies. In looking at the source I gather this is because
it assumes I'm in non-interactive mode
E.Rodichev [EMAIL PROTECTED] writes:
On Thu, 17 Feb 2005, Christopher Kings-Lynne wrote:
Fsync is so that when your computer loses power without warning, you
will have no data loss.
If you turn it off, you run the risk of losing data if you lose power.
Chris
This problem is addressed by
Christopher Kings-Lynne [EMAIL PROTECTED] writes:
This might seem like a stupid question, but since this is a massive
data loss potential in PostgreSQL, what's so hard about having the
checkpointer or something check the transaction counter when it runs
and either issue a db-wide vacuum if
Sibtay Abbas [EMAIL PROTECTED] writes:
We can call SQL statements like SPI_Execute(SELECT *
FROM sometable) from the spi interface. My question
is that can we enter other procedural languages as
well, like pgplsql statements.
You can call a function written in another procedural langauge by
Thomas Hallgren [EMAIL PROTECTED] writes:
Sibtay,
You normally don't deal with parsing, planning etc. at all from within
a language handler.
Unless you're implementing a language from scratch rather than linking
in an existing interpreter. In which case, the PL/pgSQL source is a
good
I just compiled 8.0beta5 on my old Sparc 5. All tests passed. This
is running Debian 3.0 with a 2.2.20 kernel. Sure took a long time. :)
I can test on an ia32/RedHat 6.2 machine if that would be helpful.
-Doug
---(end of broadcast)---
TIP 2:
Marc G. Fournier [EMAIL PROTECTED] writes:
No, the poster will still be included as part of the headers ... what
happens, at least under Pine, is that I am prompted whther I want to
honor the reply-to, if I hit 'y', then the other headers *are* strip'd
and the mail is set right back to the
Bort, Paul [EMAIL PROTECTED] writes:
One other thought: How does static RAM compare to disk speed nowadays?
A 1Gb flash drive might be reasonable for the WAL if it can keep up.
Flash RAM wears out; it's not suitable for a continuously-updated
application like WAL.
-Doug
Joshua D. Drake [EMAIL PROTECTED] writes:
Thank you ... I knew you guys celebrated later then us, just didn't
know why ... do you guys celebrate Remembrance Day same as us, or
different too? Ours is Nov 11 ...
I don't even know what Rememberance Day is ;)
WWI ended on November 11, 1918.
Ulrich, Azar S. [EMAIL PROTECTED] writes:
and I do have classpath set to where pg73jdbc3.jar is located via:
export CLASSPATH=.:~/lib
You need to put the JAR file itself in the classpath:
export CLASSPATH=~/lib/pg73jdbc3.jar:other stuff
-Doug
---(end of
Paul Tillotson [EMAIL PROTECTED] writes:
Given that the client does not write pages to the disk, this would be
back-end encryption. Just out of curiosity, what threat model does
this sort of encryption protect against? Surely any attacker who can
read the files off the disk can also get the
Tiago Wright [EMAIL PROTECTED] writes:
Yes, thanks Tom. This is precisely what I was missing. I searched the
archives for the reason why this is so, but I found only one message
mentioning the MVCC mechanism. Can you point me in the right
direction? I would like to understand the issue.
Alvaro Herrera [EMAIL PROTECTED] writes:
On Tue, Sep 07, 2004 at 07:58:56PM -0400, Doug McNaught wrote:
Hard to say how it would work, but come up with a good design and
quality patch and it'll probably go in. :)
Probably not. This has been discussed before; what's needed
[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 power
[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 for
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 run
it
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 it is
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 promise
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
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 that IA-32
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 error appears when
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 the password in the
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 implement a unix domain socket
driver using only Java. Is there some
[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 you
Paul Punett [EMAIL PROTECTED] writes:
Hi,
I want to concatenate a it counter to a string in a loop in plpgsql.
DECLARE
counter integer := 1;
IdSet char : = 'UniqueId'
IdForEachRun varchar;
BEGIN
IdForEachRun := IdSet || counter;(PROBLEM HERE)
IdForEachRun := IdSet || counter::text;
Shridhar Daithankar [EMAIL PROTECTED] writes:
Jokes and facts aside, I can't help it to think how better it would
have been, if postgresql was in C++. We could easily plug multiple
implementations of underlying subsystems without mucking much in base
code..
That's easy to do in any language
Nagib Abi Fadel [EMAIL PROTECTED] writes:
The issue is that since the column col1 is defined as character with
not null attribute,
shouldn't we deny such inserts (i mean inserting empty fields)???
NULL and the empty string '' are *completely* different things. If
you want to
Ivelin Ivanov [EMAIL PROTECTED] writes:
Has this subject been discussed before?
I did not find any references to it in the archives.
I think the phrase not gonna happen was invented for this subject. :)
-Doug
---(end of broadcast)---
TIP 5:
Magnus Naeslund(t) [EMAIL PROTECTED] writes:
Doug McNaught wrote:
Linux is probably killing your process because it (the kernel) is low
on memory. Unfortunately, this happens more often with older versions
of the kernel. Add more RAM/swap or figure out how to make your query
use less
Magnus Naeslund(t) [EMAIL PROTECTED] writes:
I have this big table running on an old linux install (kernel 2.2.25).
I've COPYed some tcpip logs into a table created as such:
Linux is probably killing your process because it (the kernel) is low
on memory. Unfortunately, this happens more often
Randolf Richardson [EMAIL PROTECTED] writes:
What about adding a total number of rows value to the internal
header of each table which gets incremented/decremented after each row is
INSERT/DELETE has been committed. This way, a generic count(*) by itself
could simply return this
Gaetano Mendola [EMAIL PROTECTED] writes:
Doug McNaught wrote:
Because different sessions have a (validly) different concept of what
that number should be, due to MVCC.
The count(*) information can be revisioned too, am I wrong ? I'm able to
create a trigger that store the count
Shridhar Daithankar [EMAIL PROTECTED] writes:
Tom Lane wrote:
1. You can't easily generate a clean diff of your local version against
the original imported from postgresql.org. The changes you actually
made get buried in a mass of useless $Foo$ diff lines. Stripping those
out is possible
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 library used
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 pretty much
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 darn cool app
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 of
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 considering reworking
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 the user for
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 because they
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 of just a mention in the release notes that we've found
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
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 in
the
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**=#
Ugh... pretty ugly.
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.
2. Vacuum
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 such
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 Linux
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
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 again
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])
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
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:
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 to use
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;
a
---
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)---
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
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 things
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 the
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
-I../../../../../../src/include -c -o
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'm guessing this is due
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 about
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 gigs of that.
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 tree -- i.e.
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, but not necessarily before sync() returns. I
don't think
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 sure that we
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-commanded
write
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 like XFS
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
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 are any.
ext3 with data=writeback? (See my previous message
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 close
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 single
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 readline
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 consulting.
Java PostgreSQL Enhydra Python Zope Perl
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 Enhydra Python Zope Perl Apache
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/
Custom software development, systems and network
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, systems and network consulting.
Java PostgreSQL
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.wireboard.com/
Custom software development, systems and network consulting.
Java
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 McNaught Wireboard Industries
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 BSD...
---(end of broadcast
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 Enhydra Python Zope Perl Apache Linux BSD
pg_dump. Is this true? Why would there be this limit in
pg_dump? Is it scheduled to be fixed?
This means one of two things:
1) Your ulimits are set too low, or
2) Your pg_dump wasn't compiled against a C library with large file
support (greater than 2GB).
Is this on Linux?
-Doug
--
Doug
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 development, systems and network consulting.
Java PostgreSQL
, 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 Industries http://www.wireboard.com/
Custom
. 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/
Custom software development, systems and network consulting.
Java PostgreSQL
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 from a
real database.
Hope this helps...
-Doug
--
Doug McNaught Wireboard Industries
1 - 100 of 129 matches
Mail list logo