Thank you for the help!
Regards,
Eric
On Sep 20, 2014, at 6:55 AM, Adrian Klaver wrote:
> On 09/19/2014 07:51 PM, Eric Smith wrote:
>> All,
>>
>> I created a backup using pg_dump, postgres 8.3. I'm trying to restore that
>> into a new postgres 9.3.5 i
All,
I created a backup using pg_dump, postgres 8.3. I'm trying to restore that
into a new postgres 9.3.5 installation. I just created the default text format
output with pg_dump, and am trying to restore using psql < dumpfile.
I have images saved as bytea, and I get the following error when
All,
Having a problem dumping a database using pg_dump. This is Mac OS 10.9.2 and
postgres 8.3. I'm using md5 for authentication, and have the appropriate
.pgpass file with u=rw permissions in the user's home directory. I can access
my database, called radiovision, using psql -U radiovision.
Tom,
Well... there's a lot of data hiding in each of those rows... as much as 4MB in
each. I'll make allowances in my code so that adding a column without a
default is a workable solution.
Thank you,
Eric
On Nov 1, 2011, at 8:27 PM, Tom Lane wrote:
> Eric Smith writes:
>
tring:@"\"genericInfo\" varchar(65536),"];
[tableString appendString:@"time time null,"];
[tableString appendString:@"\"saveState\" varchar(1) default \'0\',"];
[tableString appendString:@"date date null)"];
On
All,
I'm adding a column in postgres 8.3 with the syntax: alter table images add
column "saveState" varchar(1) default '0'; It takes a good solid 20 minutes to
add this column to a table with ~ 14,000 entries. Why so long? Is there a way
to speed that up? The table has ~ 50 columns.
Thank
OK... never mind, everyone. The problem was elsewhere in the code.
Regards,
Eric
On May 25, 2009, at 5:31 PM, Tom Lane wrote:
Eric Smith writes:
Seems to work just fine. If, on the other hand, I issue the same
command from within the C API:
NSString* query = [NSString stringWithFormat
Very interesting.
when I set log_statement='all', I see entries for various queries, but
I see nothing for the query I list below. If I just use printf() to
print out the c-string, it looks just like all the other queries.
Eric
On May 25, 2009, at 5:31 PM, Tom Lane wrote:
Alrighty so, how do I turn on log_statement?
Thanks,
Eric
On May 25, 2009, at 5:31 PM, Tom Lane wrote:
Eric Smith writes:
Seems to work just fine. If, on the other hand, I issue the same
command from within the C API:
NSString* query = [NSString stringWithFormat:@"SELECT us
message is:
status=PGRES_FATAL_ERROR error=<>
I'm connecting to the database through a host IP address, not through
localhost. So, why does this break?
Thanks,
Eric
On May 10, 2009, at 8:39 AM, Tom Lane wrote:
Eric Smith writes:
You are correct. On an Intel, the failed comman
Tom,
Thanks for the detailed info... makes my life a lot easier!
Eric
On May 9, 2009, at 7:07 PM, Tom Lane wrote:
I wrote:
That isn't exactly a trivial thing to do, because the pg_config.h
data
differs for the two arches. It will *not* work to just run a basic
configure and build with CFL
er on the PPC. I'll look through
the archives as you suggest.
Regards,
Eric
On May 9, 2009, at 6:37 PM, Tom Lane wrote:
Eric Smith writes:
You bet... here you go.
Hmm, I see you are trying to build universal binaries:
CFLAGS=-arch i386 -arch ppc ...
That isn't exactly a tr
-rpath,@loader_path/../lib
LDFLAGS_SL =
LIBS = -lpgport -lz -lreadline -lm
VERSION = PostgreSQL 8.3.5
On May 9, 2009, at 6:08 PM, Tom Lane wrote:
Eric Smith writes:
I actually started with the source: postgresql-8.3.5.tar.gz, from the
source download location. I just build straight from that
I actually started with the source: postgresql-8.3.5.tar.gz, from the
source download location. I just build straight from that source...
no mucking around with any of the sources.
Eric
On May 9, 2009, at 5:44 PM, Tom Lane wrote:
Eric Smith writes:
Yep, using that command gives me the
Yep, using that command gives me the error.
I'm using a build that came from the postgres website, and just uses
the config that comes with it.
Eric
On May 9, 2009, at 5:16 PM, Tom Lane wrote:
Eric Smith writes:
When I try the command below, I get the very familiar error:
&quo
All,
When I try the command below, I get the very familiar error: "expected
just one rule action"
I'm running 8.3.5 on Mac OS 10.5.6.
Any ideas?
Thanks,
Eric
On May 7, 2009, at 11:24 PM, Albe Laurenz wrote:
Eric Smith wrote:
How do I get a list of database usernames usi
Never mind, everyone. I figured it out.
On May 7, 2009, at 8:05 PM, Eric Smith wrote:
All,
How do I get a list of database usernames using the postgres C API?
Thanks,
Eric
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http
All,
How do I get a list of database usernames using the postgres C API?
Thanks,
Eric
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
Tried this out, and got a very familiar error that I don't know what
to do with : "Error: expected just one rule action".
I'm using 8.3.5, and see this error quite a bit. Anyone know what's
behind this error?
Thanks,
Eric
On Apr 8, 2009, at 8:54 PM, John R P
All,
From the C API, how do I check for the existence of a column name in
a given table?
Thanks,
Eric
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
Bingo!
I doubled each of the entries below, and the two servers are now
running together quite happily!
Regards,
Eric
On Mar 30, 2009, at 7:56 PM, Eric Smith wrote:
... as a reminder, this is running on mac os 10.5
Eric
On Mar 30, 2009, at 7:53 PM, Eric Smith wrote:
Ahhh! Can't
... as a reminder, this is running on mac os 10.5
Eric
On Mar 30, 2009, at 7:53 PM, Eric Smith wrote:
Ahhh! Can't seem to make this go away!
Here is the log file entry:
FATAL: could not create shared memory segment: Cannot allocate memory
DETAIL: Failed system call was shmget(key=54
the same error. Should I
be bumping these numbers up?
Eric
On Mar 30, 2009, at 7:18 PM, Tom Lane wrote:
Eric Smith writes:
Log file says "could not create shared memory segment". It also says
that I should change max_connections or shared_buffers.
Error message claims that m
ers is 300, but postgresql.conf
has this listed as 2400kB.
What the heck is going on here? (no, the lines in the conf file are
not commented out). How do I enforce the conf file entries?
Thanks,
Eric
On Mar 29, 2009, at 8:19 PM, Tom Lane wrote:
Eric Smith writes:
Yes, if I start one, but not
pm Eric Smith wrote:
All,
I'm trying to run two database clusters on a single machine, and am
failing. I use initdb to create the two clusters... each has their
own directory structure. I can start one server or the other with
pg_ctl, but once the first starts, the second just hangs on &qu
Yes, if I start one, but not the other, the process works just great.
It's only when trying to run both that I have a problem.
Thanks,
Eric
On Mar 28, 2009, at 3:37 PM, Adrian Klaver wrote:
On Saturday 28 March 2009 3:27:15 pm Eric Smith wrote:
All,
I'm trying to run tw
All,
I'm trying to run two database clusters on a single machine, and am
failing. I use initdb to create the two clusters... each has their
own directory structure. I can start one server or the other with
pg_ctl, but once the first starts, the second just hangs on "waiting
for server t
All,
I'm trying to run two database clusters on a single machine, and am
failing. I use initdb to create the two clusters... each has their
own directory structure. I can start one server or the other with
pg_ctl, but once the first starts, the second just hangs on "waiting
for server t
28 matches
Mail list logo
