Matthew Wilson wrote:
I have a lot of code -- millions of lines at this point, written
over the last 5 years. Everything is in a bunch of nested folders.
At least once a week, I want to find some code that uses a few modules,
so I have to launch a find + grep at the top of the tree and then
Hi,
sorry for late response and lack of details. Postgresql version is 8.2.5 .
This is how to reproduce this issue:
inh_test=# CREATE TABLE cities (
inh_test(# id serial,
inh_test(# nametext,
inh_test(# population float,
inh_test(# altitudeint -- in
Adrian Klaver wrote:
I might be missing the point, but couldn't you do a Copy to a single table
instead of multiple inserts and avoid the index overhead.
Are you saying, have one large table with indexes and do a COPY to it or
are you saying a one small empty table and do a COPY to it?
On Oct 27, 2007, at 3:02 PM, Seneca Cunningham wrote:
On Sat, Oct 27, 2007 at 12:56:37PM -0500, Perry Smith wrote:
On my Mac systems, this work. On my AIX system it does not. I get:
createdb dog -E utf8
createdb: too many command-line arguments (first is utf8)
Try createdb --help for more
On Oct 28, 2007, at 12:59 AM, Guy Rouillier wrote:
Matthew Wilson wrote:
I have a lot of code -- millions of lines at this point, written
over the last 5 years. Everything is in a bunch of nested folders.
At least once a week, I want to find some code that uses a few
modules,
so I have to
Perry-
Does cscope support PHP?
Thanks for the link
M--
- Original Message -
From: Perry Smith [EMAIL PROTECTED]
To: Guy Rouillier [EMAIL PROTECTED]
Cc: pgsql-general@postgresql.org
Sent: Sunday, October 28, 2007 10:25 AM
Subject: Re: [GENERAL] I want to search my project source code
On Oct 28, 2000, at 9:41 AM, Martin Gainty wrote:
Perry-
Does cscope support PHP?
I don't think so. Exuberant tags suppose a lot of languages but it
does not do references (I think) -- just definitions.
Thanks for the link
M--
- Original Message -
From: Perry Smith [EMAIL
Sebastjan Trepca [EMAIL PROTECTED] writes:
This is how to reproduce this issue:
...
inh_test=# alter table capitals inherit cities;
Fascinating. pg_dump is almost smart enough to get this right, except
that what it spits out is
ALTER TABLE capitals ALTER COLUMN id SET DEFAULT
-- Original message --
From: Thomas Finneid [EMAIL PROTECTED]
Adrian Klaver wrote:
I might be missing the point, but couldn't you do a Copy to a single table
instead of multiple inserts and avoid the index overhead.
Are you saying, have one large
Please help.
I am attempting to restore a database into PostgreSQL version 8.2 running on
Win XP Professional.
From the 'bin' folder, I am using the command line-
pg_restore psql -h localhost -d PDW -U postgres -f aurel.sql
I get an error -
pg_restore: cannot specify both -d and -f
On Sunday 28 October 2007 11:32 am, Bob Pawley wrote:
Please help.
I am attempting to restore a database into PostgreSQL version 8.2 running
on Win XP Professional.
From the 'bin' folder, I am using the command line-
pg_restore psql -h localhost -d PDW -U postgres -f aurel.sql
Try
Adrian Klaver wrote:
I'm thinking do a COPY to one large table. If the cost of indexing is relatively fixed as
you indicated in your previous post then you reduce the indexing overhead to each
COPY operation instead of each insert.
No, what I meant whas that creating an index on a table
Perry Smith [EMAIL PROTECTED] writes:
The getopt_long on Mac and I guess also Linux have been made non-
Posix compliant. They accept options after the non-option argument. What is
really disturbing is they alter argv. I find that somewhat a bad idea but, I
guess no one really cares
Hi Adrian
With pg_restore psql -h localhost -d PDW -U postgres aurel.sql the error
message is -
pg_restore: could not open input file: No such file or directory exists.
I get this message with aurel.sql - or aurel - or the path to aurel
(..8,2\bin) or when aurel is not even
On Sunday 28 October 2007 2:13 pm, Bob Pawley wrote:
Hi Adrian
With pg_restore psql -h localhost -d PDW -U postgres aurel.sql the error
message is -
pg_restore: could not open input file: No such file or directory exists.
I get this message with aurel.sql - or aurel - or the path to
Bob Pawley [EMAIL PROTECTED] writes:
This is becoming quite frustrating.
The errant psql is your problem ... although pg_restore is being
quite unhelpful by not mentioning the filename that it's trying to open.
regards, tom lane
---(end of
On Sunday 28 October 2007 2:28 pm, Tom Lane wrote:
Bob Pawley [EMAIL PROTECTED] writes:
This is becoming quite frustrating.
The errant psql is your problem ... although pg_restore is being
quite unhelpful by not mentioning the filename that it's trying to open.
The latest in the saga -
By using - pg_restore -h localhost -d PDW -U postgres aurel.sql
I get the message - pg_restore: input file does not appear to be a valid
archive.
I get this message when I used the aurel.sql file which I previously loaded
successfully in 8.1 and also when I use an
On Sunday 28 October 2007 3:01 pm, Bob Pawley wrote:
The latest in the saga -
By using - pg_restore -h localhost -d PDW -U postgres aurel.sql
I get the message - pg_restore: input file does not appear to be a valid
archive.
I get this message when I used the aurel.sql file which I
Bob Pawley [EMAIL PROTECTED] writes:
The latest in the saga -
By using - pg_restore -h localhost -d PDW -U postgres aurel.sql
I get the message - pg_restore: input file does not appear to be a valid
archive.
Oh, I just twigged that you are using a plain-SQL dump file (that is,
you didn't
This is the dump command
pg_dump -h localhost -d Aurel -U postgres
Could you suggest a dump command that will match the restore command -
pg_restore -h localhost -d PDW -U postgres aurel.sql
Thanks
Bob
- Original Message -
From: Adrian Klaver [EMAIL PROTECTED]
To:
On Sunday 28 October 2007 3:40 pm, Bob Pawley wrote:
This is the dump command
pg_dump -h localhost -d Aurel -U postgres
Could you suggest a dump command that will match the restore command -
pg_restore -h localhost -d PDW -U postgres aurel.sql
Thanks
Bob
It depends on what you want
On 28/10/2007 22:40, Bob Pawley wrote:
pg_dump -h localhost -d Aurel -U postgres
Could you suggest a dump command that will match the restore command -
pg_restore -h localhost -d PDW -U postgres aurel.sql
One thing that caught me, and I suspect may be catching you also -
somewhat
Tom Lane wrote on 28.10.2007 23:18:
Oh, I just twigged that you are using a plain-SQL dump file (that is,
you didn't specify -Fc or -Ft to pg_dump). For plain-SQL dumps you
should not use pg_restore at all; you feed those to psql.
While we are on the topic of pg_dump/pg_restore:
Why is it,
Thomas Kellerer [EMAIL PROTECTED] writes:
Why is it, that pg_dump can use a compressed output directly but pg_dumpall
is
always using a SQL (i.e. plain text) output?
The custom and tar formats are not designed to support data from more
than one database. At some point somebody should
Alexander Staubo schrieb:
On 10/27/07, Bob Pawley [EMAIL PROTECTED] wrote:
I would like to try PostgreSQL 8.3 without uninstalling version 8.1.
Is this possible??
Sure. If you're on Unix, download the source and install it somewhere
in, say, your home directory. This requires a
Tom Lane wrote:
Bob Pawley [EMAIL PROTECTED] writes:
The latest in the saga -
By using - pg_restore -h localhost -d PDW -U postgres aurel.sql
I get the message - pg_restore: input file does not appear to be a valid
archive.
Oh, I just twigged that you are using a plain-SQL dump file
27 matches
Mail list logo
