Jeff Frost wrote:
> Tena Sakai wrote:
>>
>> > If you want to restore all the databases that were in this
>> > postgresql installation at the time of the backup, then the
>> > best thing to do is drop all those DBs before attempting the
>> > restore.
>> Yes, the database in question is built and u
Tena Sakai wrote:
>
> > If you want to restore all the databases that were in this
> > postgresql installation at the time of the backup, then the
> > best thing to do is drop all those DBs before attempting the
> > restore.
> Yes, the database in question is built and updated continuously
> from a
Hi Jeff,
Thanks for getting back to me.
> Do the databases you are trying to restore already exist?
Yes.
> If so, restoring from a dumpall file won't work out very
> well for you.
Mmm...
> What exactly are you trying to restore?
> Perhaps you only want to restore a few tables?
No. Please read
On Fri, 22 Aug 2008, Tena Sakai wrote:
Hi,
I am in a fix...
I have executed the following command being a user postgres:
zcat /var/postgres/backup/20080812.2.gz | psql postgres > restore.out 2 >
restore.err
It asked me a password, which I complied. It worked silently
for a couple of hours a
Hi,
I am in a fix...
I have executed the following command being a user postgres:
zcat /var/postgres/backup/20080812.2.gz | psql postgres > restore.out 2 >
restore.err
It asked me a password, which I complied. It worked silently
for a couple of hours and told me:
Segmentation fault
As I loo
Many thanks, Jeff. I appreciate it. (And I will take
this opportunity to look at the dump file, if nothing
else, to satisfy my curiosity.)
Regards,
Tena Sakai
[EMAIL PROTECTED]
-Original Message-
From: Jeff Frost [mailto:[EMAIL PROTECTED]
Sent: Fri 8/22/2008 3:54 PM
To: Tena Sakai
Cc:
On Fri, 22 Aug 2008, Tena Sakai wrote:
Many thanks, Jeff.
I am now clued in as to what "postgres" means in the
context of "psql -f infile postgres". Also, thanks
for a tip for stdout and stderr redirection.
What I am still a bit shaky is whether or not I should
issue "createdb" prior to resto
Many thanks, Jeff.
I am now clued in as to what "postgres" means in the
context of "psql -f infile postgres". Also, thanks
for a tip for stdout and stderr redirection.
What I am still a bit shaky is whether or not I should
issue "createdb" prior to restore. I would appreciate
it if you could el
On Fri, 22 Aug 2008, Tena Sakai wrote:
Hi Everybody,
I had a machine crash a couple of days ago, from which
I have recovered (ie., postgres is running now), but I
want to restore from a dump I had made. The dump is
made by pg_dumpall and I have a gzipped file.
I am a bit unclear as to how to
Hi Everybody,
I had a machine crash a couple of days ago, from which
I have recovered (ie., postgres is running now), but I
want to restore from a dump I had made. The dump is
made by pg_dumpall and I have a gzipped file.
I am a bit unclear as to how to proceed.
(A) I get rid of what I have now
Postgres, like any descent RDBMS, performs an auto instance crash
recovery using its transaction logs.
Regards,
Husam
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of c k
Sent: Friday, August 22, 2008 11:02 AM
To: [EMAIL PROTECTED]; pgsq
Thanks
CPK
On Fri, Aug 22, 2008 at 11:36 PM, Tomeh, Husam <[EMAIL PROTECTED]>wrote:
> Postgres, like any descent RDBMS, performs an auto instance crash
> recovery using its transaction logs.
>
>
>
> Regards,
>
> Husam
> --
>
> *From:* [EMAIL PROTECTED] [mailto
Hello all,
As I know and have seen that innodb engine of MySQL does an auto-recovery
when MySQL server is crashed or due to power failure. What is with
postgreSQL? Does it makes an auto-recovery? and how?
Thanks
CPK
Hello,
I am trying to run a silent install (no upgrade) of v 8.3.3 using the
following switches:
msiexec.exe /log errorfile.log /i postgresql-8.3.msi /qn
ADDLOCAL=server,psql,docs SERVICEDOMAIN="%COMPUTERNAME%"
SERVICEPASSWORD="admin" SUPERPASSWORD="admin"
The install fails with the following
Hello,
I am trying to run a silent install (no upgrade) of v 8.3.3 using the
following switches:
msiexec.exe /log errorfile.log /i postgresql-8.3.msi /qn
ADDLOCAL=server,psql,docs SERVICEDOMAIN="%COMPUTERNAME%"
SERVICEPASSWORD="admin" SUPERPASSWORD="admin"
The install fails with the following
On Fri, Aug 22, 2008 at 06:33:50AM -0700, CG wrote:
> cluster, and I'm finidng that it is REALLY easy for the two
> back-ends to get out of sync with each other.
When I investigated that product, I came to the conclusion that it's
in the family of replication by query-dispatch. Everything in th
On Fri, Aug 22, 2008 at 03:52:39PM +0200, RW wrote:
> It seems that we have to wait for PGCluster-II which isn't a
> "shared nothing" solution. Instead all files are on a shared
> medium like SAN or iSCSI and all instances uses this medium
> (similar to Oracle).
That's not shared-nothing, it's sh
Maybe some people haven't read this site here:
http://www.postgresqldocs.org/wiki/Replication,_Clustering,_and_Connection_Pooling
It gives a nice overview. Another interesting project which isn't
production ready yet is Postgres-R (http://www.postgres-r.org/)
Robert
RW wrote:
I hoped that it
I hoped that it would be easier to get the nodes back in sync
but it seems that all Postgres Multi-Master solutions are not
reliable at the moment. I've planed to test CyberCluster
this weekend but I already suspected that this rsync solutions
have some shortcomings. Sniff...
It seems that we hav
I've been testing Cybercluster (which is a modified PgCluster) ... I have two
back-end databases, one load balancer, and one replicator. I've been testing
failover and rebuilding a degraded cluster, and I'm finidng that it is REALLY
easy for the two back-ends to get out of sync with each other.
Thanks to all,
I will try to use tsearch2 with some other index and then reply.
Regards,
CPK
On Fri, Aug 22, 2008 at 5:01 PM, Tino Wildenhain <[EMAIL PROTECTED]> wrote:
> Hi,
>
> c k wrote:
>
>> Hello all,
>> As we are migrating our ERP application from MySQL to PostgreSQL we have
>> some difficu
Hi,
c k wrote:
Hello all,
As we are migrating our ERP application from MySQL to PostgreSQL we have
some difficulties. One of them is use of Like and Similar to operators.
We often use LIKE to search a string from front-end without case
sensetivity. As postgreSQL's LIKE is case sensitive, we t
Hello all,
As we are migrating our ERP application from MySQL to PostgreSQL we have
some difficulties. One of them is use of Like and Similar to operators. We
often use LIKE to search a string from front-end without case sensetivity.
As postgreSQL's LIKE is case sensitive, we tried ILIKE and SIMILA
It does not seem correct. If 'ta, a' and 'ta, b' is minor to 'tab, a'.
you should not get that order.
This is my result and what i think is what you expect.
CREATE TABLE sorting (name varchar);
labb=# \d sorting
Table "public.sorting"
Column | Type| Modifiers
+
24 matches
Mail list logo
