Hi.
After looking again at the other email I've sent earlier, I realized that it
goes on for far too long, so I'll try to summarize my question more briefly.
1) How can FTI be made to NOT break up words into sub-strings? Most of those
are likely to be useless in my particular application. In f
On Thu, 18 Oct 2001, [iso-8859-1] Flávio Brito wrote:
> Hi ALL
>
> I imported a database from Access 2000 to Postgre for Windows but now I can't
> backup my database to export to Postgre for Linux .
> I tried to use pg_dumpall > db.sql, its freeze on Windows2000 for more than a
> hour. My databas
Off the top of my head, I don't recall any specific 'middleware'
implementations that do this exactly, but it wouldn't be entirely difficult
to make one of your own. If you are familiar with Perl or Python, making a
parallel processing network server is not rocket science, and you have
complete co
"Andrew Crouch" <[EMAIL PROTECTED]> writes:
> -rw--- 1 postgres dbadmin 122880 Oct 18 13:28 1269 <-- What is this
> file
pg_log, as you could find out with an inquiry against pg_class:
test71=# select relname from pg_class where relfilenode = 1269;
relname
-
pg_log
(1 row)
te
[Broken SQL instead of performance issue fixed]
It would appear that when I define the index on the FTI table (string and
oid) to be unique (which makes sense, since there is little point in having
duplicate rows in this case), a lot of inserts fail where they shouldn't. I
am guessing that if
Bruce Cota <[EMAIL PROTECTED]> writes:
> Is there a way, in SQL, to access the oid of the row created
> by an immediately preceding insert statement?
If you are writing a psql script, recent psql versions maintain
a LASTOID variable:
regression=# insert into int4_tbl default values;
INSERT 33574
Take a look at www.postgresql.org/docs/index.php?datatype-character.html. Be
sure to take a look at the comments at the bottom of the page. The
documentation agrees with you, but Peter Eisentraut gives a different take.
-Original Message-
From: Brett W. McCoy [mailto:[EMAIL PROTECTED]]
I am running PostgreSQL 7.1.3, RedHat 7.1
(kernel 2.4.2-2), and PHP/4.0.4pl1.
When I try to run a PHP page found below I get an error that says:
Fatal error: Call to undefined function: pg_connect()
in /var/www/html/psolver.php on
line 10
Additionally,
even though pgsql.so IS in
On Thu, Oct 18, 2001 at 10:29:09AM -0400, Bruce Cota wrote:
> Thank you!
>
> Hopefully that getlastoid refers to the last oid
> created in this session or transaction? I can't find it
> mentioned in the docs anywhwere.
last insert, iirc.
> Nextval and curval aren't specific to the transaction
Last night postmaster crashed while running a lengthy querry.
The message I found was that a log file grew too big.
Postmaster was down. I tried to restart it , but it would not. I restarted
the system, but it would not start either.
Manual start with a log file:
FATAL 1: configuration file `post
On Thu, 18 Oct 2001, David Pirotte wrote:
> Allan Engelhardt wrote:
> >
> > Sorry for the offtopic nature, but:
> >
> > 1. Am I the only one who are having problems with the listerver not honouring the
>NOMAIL option?
> > I prefer to read the list on news and am a little annoyed with the vol
Hi everyone.
Just got postgres 7.1.3 (debian unstable) going after an upgrade from
7.0.x. I have things *mostly* working now, with a few questions
regarding authentication.
What I'd like to have is the following two situations dealt with:
- unsupervised backups using something like pg_dumpall
On Thu, 18 Oct 2001, [iso-8859-2] Micha³ 'Samuel' Modestowicz wrote:
> I know that my question may seem trivial, but unfortunately I haven't found
> any understandable info on this topic. It's about length limit of the TEXT
> field in PostgreSQL. I've heard that the TEXT fields in psql are limite
Hi All
I want protocol descriptions of Postgresql 7.1 I
mean how Postgres listens request at default port 5432. If one wants to write to
execute some query using its program(like in C, java) directry by sending data
at server socket 5432 then how this task can be achieved. Can anybody tell me
Hi ALL
I imported a database from Access 2000 to Postgre for Windows but now I can't
backup my database to export to Postgre for Linux .
I tried to use pg_dumpall > db.sql, its freeze on Windows2000 for more than a
hour. My database has 6 MB.
I can backup my database directory on Windows (us
Indeed, the problem has been tracked down to hardware. Bad RAM. I was (with
the kind help of some list members) able to rebuild the database without any
data loss.
Basically, what I had to do was update 'pg_class->relnatts' from 19 to 18.
This single change allowed me to actually work with
Hi!
First, sorry if this is off topic. Second, WARNING: broken english
ahead :)
Is it possible to create a 'custom' server which can accept normal
connections from normal clients, but use different language (or just
'proxy' the queries to the real server)? A friend of mine told
is there a trick to drop a column in a table ? or do I need to
recreate the table and drop the old one ?
thnx,
peter
--
mag. peter pilsl
phone: +43 676 3574035
fax : +43 676 3546512
email: [EMAIL PROTECTED]
sms : [EMAIL PROTECTED]
pgp-key available
---(end of broadc
Greetings, Bruce!
At 18.10.2001, 02:34, you wrote:
>> Isn't it much worse to not follow PostgreSQL behavior than to not follow
>> MySQL behavior?
BM> Another idea: because our historical Limit #,# differs from MySQL, one
BM> idea is to disable LIMIT #,# completely and instead print an error
BM
Bruce Momjian wrote:
>>Bruce Momjian writes:
>>
>>
Break the SQL code that has been implemented for prior versions??
Bummer ;((.
>>>Yes, but we don't follow the MySQL behavior, which we copied when we
>>>added LIMIT. Seems we should agree with their implementation.
>>>
>>Isn't it m
On Sat, 13 Oct 2001 07:13:25 -0700 (PDT)
Stephan Szabo <[EMAIL PROTECTED]> wrote:
> Well, that's difficult. The spec is very hard to understand about
> that. I believe we determined that our behavior was very very
> close to complient, but that it does not match the standard
> reading of that
> I know that my question may seem trivial, but unfortunately I haven't found
> any understandable info on this topic. It's about length limit of the TEXT
> field in PostgreSQL. I've heard that the TEXT fields in psql are limited to
> 4096 bytes but it's just unbelievable for me. So if I've got te
22 matches
Mail list logo
