* Tom Lane <[EMAIL PROTECTED]> [000526 15:43] wrote:
> "Bryan White" <[EMAIL PROTECTED]> writes:
> 4, I could probably get by with just 2 If I had to. I will give it a
> try.
>
> > With the indexes deleted I am now getting 40 or 50 updates per second
> > instead of 5.
>
> That's good,
Barry Lind <[EMAIL PROTECTED]> writes:
> I am curious, how does PostgreSQL support tables larger than 2Gig, given
> the file per table architecture?
Multiple files per table ...
regards, tom lane
[EMAIL PROTECTED] writes:
> I recently compiled and installed PostgreSQL 7.0 on a P-III workstation
> running SuSE Linux 6.2 (2.2.10 kernel, gcc ver. 2.7.2.3). The compilation
> completed with some non-fatal warnings, but when I ran the sequential
> regression tests, five failures occurred.
> I a
--snip--
Yes, I like the Idea of picking from a list if you get a return > 1.
off topic:
The main point of this whole little project was to design a SQL
database and make a Web interface to it. One of my main goals
was to learn the how and why's of SQL. My Zope skill are sub par
also, so
On Fri, 26 May 2000, Mike Mascari wrote:
> Ron Peterson wrote:
> > After installation, shouldn't everything you need be in
> > /usr/local/pgsql?
Too many assumptions are in the source that the source will always be there.
Not necessarily true!
> I too have run into this dependency problem. The
On Fri, 26 May 2000, Tom Lane wrote:
> Ron Peterson <[EMAIL PROTECTED]> writes:
> > After installation, shouldn't everything you need be in
> > /usr/local/pgsql?
> Yeah, it should really. We've had this discussion before. The real
> problem is that no one wants to install the entire pgsql incl
Lamar Owen <[EMAIL PROTECTED]> writes:
> /lib/cpp -M -I. -I../backend executor/spi.h |xargs -n 1|grep \\W|grep -v ^/|grep -v
>spi.h | sort |cpio -pdu $RPM_BUILD_ROOT/usr/include/pgsql
> This could easily enough be included in the make install, couldn't it?
> (Tom? Anyone?) I realize that GNU g
char_length() no longer seems to be working for me (at least with my
current build).
For example, create a simple test table and populate it with some
values:
CREATE TABLE test (
f1 character(4)NOT NULL,
f2 varchar(20),
PRIMARY KEY (f1)
);
INSERT IN
