Hi all,
I'm looking for a way to get DBF tables into Postgres. I have been attempting
to compile pg2xbase without success. Does anyone feel kind enough to provide
the utility already compiled. I'm using SUSE 9.0. Again I'm not asking for
help in compiling but an RPM or something that already
"G. Frank Liu" <[EMAIL PROTECTED]> writes:
> $ psql -U gforge gforge
> psql: FATAL: Invalid page header in block 3 of pg_trigger_tgrelid_tgname_index
> Any ideas how I can fix it?
See the REINDEX man page. In 7.3 I think you have to go through the
full run-a-standalone-backend pushup to reindex
On Sun, 28 Mar 2004, Mike Nolan wrote:
> The \l command should only list databases that the current user is
> authorized for, the \du command should only list users authorized for
> the current database (and perhaps only superusers should get even that
> much information), etc. Perhaps it is poss
On Sun, 28 Mar 2004, Mike Nolan wrote:
> > Huh? Each database under PostgreSQL is kept under a seperate directory on
> > the server ... always has been that way ..
>
> Perhaps, but it isn't obvious which directory has which database. I'm not
> not sure which system catalogs provide that informat
Alex wrote:
MySQL is still the default database offered by any web hosting company
and if Postgres wants to become the designated db engine for these
services or become the worlds no.1 open source db then i think lots of
things need to be done. Take for example the admin interface (MySQL
Admini
> Just curious ... restricting \l itself isn't too difficult ... but how
> does MySQL restrict the ability to do something like:
>
> SELECT datname FROM pg_database;
>
> or does it not have an equivalent to that?
I'm not much of an expert in MySQL, but on my ISP 'show databases' only
shows MY d
Tom Lane wrote:
This script is lacking a VACUUM or ANALYZE command, so the planner
doesn't know how large the table is. Note the ridiculously small
cost estimates in EXPLAIN ...
I see, I never knew about having to VACUUM/ANALYZE first. Thanks.
--
dave
---(end of broadcast)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Sunday 28 March 2004 06:06 pm, Alex wrote:
> Frank,
> pls. apologize. Maybe my description was not so clear. What I was
> referring to was the fact that under MySQL you have more freedom to give
> individual users of a shared server rights to create
> > Perhaps, but it isn't obvious which directory has which database. I'm not
> > not sure which system catalogs provide that information, something that
> > wasn't obvious from the online docs, either.
>
> SELECT oid FROM pg_database WHERE datname = '';
Thanks. That should be easier to find in
I have problems connecting to my gforge database (http://gforge.org).
It's been working fine, and now
$ psql -U gforge gforge
psql: FATAL: Invalid page header in block 3 of pg_trigger_tgrelid_tgname_index
Any ideas how I can fix it?
(I am running postgresql v7.34)
Thanks!
---
> Huh? Each database under PostgreSQL is kept under a seperate directory on
> the server ... always has been that way ..
Perhaps, but it isn't obvious which directory has which database. I'm not
not sure which system catalogs provide that information, something that
wasn't obvious from the onli
On Mon, 29 Mar 2004, Alex wrote:
> Frank,
> pls. apologize. Maybe my description was not so clear. What I was
> referring to was the fact that under MySQL you have more freedom to give
> individual users of a shared server rights to create and manage their
> databases In addition all databases are
Frank,
pls. apologize. Maybe my description was not so clear. What I was
referring to was the fact that under MySQL you have more freedom to give
individual users of a shared server rights to create and manage their
databases In addition all databases are kept in separate directories
unlike pos
Anyone had any problems with the bugs mailing list? I posted a message
to it on friday lunchtime (australian time) and didn't get anything back
for it. I reposted it using the web page bug report and didn't see it
either.
It's possible that my file was rejected due to an attachment as the test
c
Sean Chittenden <[EMAIL PROTECTED]> writes:
> The first part I knew, but the historical behavior mentioned is
> interesting... I haven't run into a naming conflict yet, but will
> probably change things to preemptively thwart such problems. This
> oddity seems pretty unknown and certainly not s
David Garamond <[EMAIL PROTECTED]> writes:
> 1. script to create the test table (a 1mil-record table; each record
> contains 1-40 random bytes):
This script is lacking a VACUUM or ANALYZE command, so the planner
doesn't know how large the table is. Note the ridiculously small
cost estimates in E
Hi,
I’ve been working with Postgres for about a year, so I’m little
better than a newbie with Postgres’ internal architecture or its means of
getting tricksy things done. I’ve experience in Linux working with PostgreSQL
7.3, stored procedures in PL/pgSQL, and writing specialized shared
[snip function bits]
The first part I knew, but the historical behavior mentioned is
interesting... I haven't run into a naming conflict yet, but will
probably change things to preemptively thwart such problems. This
oddity seems pretty unknown and certainly not something I recall having
read
Tom Lane wrote:
David Garamond <[EMAIL PROTECTED]> writes:
The table contain +- 1 mil records, all of the actual version of the
queries below return < 10 rows, so an index should be used. Using an
index scan, the query ran < 100ms. Using seq scan, 2-3 secs. So there is
no good reason why a seq
Sean Chittenden <[EMAIL PROTECTED]> writes:
> CREATE FUNCTION f1(RECORD) RETURNS BOOL LANGUAGE 'plpgsql' AS 'BEGIN
> RETURN TRUE; END;';
You can't use RECORD as the declaration of a plpgsql function parameter,
only as its result type. (Although I wonder whether we couldn't treat
it as a sort of
On Sun, 28 Mar 2004 20:08:11 +0700 David Garamond <[EMAIL PROTECTED]> sat down, thought
long and then wrote:
> I for one vote for win32 users having their own list as soon as
> possible. I predict three things:
>
> 1) there will be *lots* of them coming to -general (instead of to -novice);
> 2)
David Garamond <[EMAIL PROTECTED]> writes:
> The table contain +- 1 mil records, all of the actual version of the
> queries below return < 10 rows, so an index should be used. Using an
> index scan, the query ran < 100ms. Using seq scan, 2-3 secs. So there is
> no good reason why a seq scan shou
David Garamond said:
> Bruce Momjian wrote:
> So can I quietly beg the Win32 group to expedite this port. I believe
> you will be utterly astonished at the demand. Please.
> >>
> >>Speaking of win32 port, do/will we need a win32 users list
> >>(pgsql-win32)? MySQL has one. For now, I
Can multiple SQL statements
be concatenated with separating semicolons, prepared with a single
statement, and executed with a single statement? This implies that parameter $1
could be used in statement 2 & 4, ...
My interface is libpq
Thanks
Rob
How does one use a prepared select statement
as outlined in the documents under the prepare statement. I need an example how
to convert the plan to cursor so the results can be pulled.
My environment is linpq Version 7.2 Linux
X86.
Thanks
Bruce Momjian wrote:
So can I quietly beg the Win32 group to expedite this port. I believe
you will be utterly astonished at the demand. Please.
Speaking of win32 port, do/will we need a win32 users list
(pgsql-win32)? MySQL has one. For now, I think such a list can assert to
the world that a
Hopefully I'm being blind and missing something obvious. Here's the
scenario:
-- I have a large table/view with a large-ish number of columns
(routinely
-- more than 32 cols) and need to pass every col through to a function,
and
-- am not inclined to recompile with INDEX_MAX_KEYS/FUNC_MAX_ARGS
The table contain +- 1 mil records, all of the actual version of the
queries below return < 10 rows, so an index should be used. Using an
index scan, the query ran < 100ms. Using seq scan, 2-3 secs. So there is
no good reason why a seq scan should be used, especially in a case of
b='foo' or b='
28 matches
Mail list logo
