n guidelines for filesystem backups of a
> running PG database ?
The data is correct and non-contradictory. The problem is that you're
reading two different documents on two different methods of making
backups. The methods have different rules that must be followed to
get a good backup.
se someone is worried that there may be some
validity to the complaint:
I use FreeBSD/Firefox 2 and I don't have any trouble
having many, many tabs open and pointing to various parts of
the pg.org site. I also don't use Flash and don't know what
he's talking about.
--
Bill M
In response to "Janardhanachari, Jagadeesha" <[EMAIL PROTECTED]>:
> What is the password for postgres ?
There is none. Please read:
http://www.postgresql.org/docs/8.3/static/client-authentication.html
Then take any further discussion on the matter to the pgsql-general@
mail
stats gathering, I use mrtg, which I like
because it's very flexible.
--
Bill Moran
Collaborative Fusion Inc.
http://people.collaborativefusion.com/~wmoran/
[EMAIL PROTECTED]
Phone: 412-422-3463x4023
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
#x27;t a bug in PostgreSQL. I don't believe it's a bug at all, it's
just an interoperability quirk.
--
Bill Moran
Collaborative Fusion Inc.
http://people.collaborativefusion.com/~wmoran/
[EMAIL PROTECTED]
Phone: 412-422-3463x4023
--
Sent via pgsql-bugs mailing list (pgsql-bugs@pos
y the same
thing from the server's perspective.
--
Bill Moran
Collaborative Fusion Inc.
http://people.collaborativefusion.com/~wmoran/
[EMAIL PROTECTED]
Phone: 412-422-3463x4023
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
ct you're confusing PostgreSQL with another SQL product. Are you
sure you're reporting this problem to the correct people?
--
Bill Moran
Collaborative Fusion Inc.
http://people.collaborativefusion.com/~wmoran/
[EMAIL PROTECTED]
Phone: 412-422-3463x4023
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
to get things back under control. If it's really bad, you may
be better off doing a dump/restore as it may be considerably faster.
Are you sure your database hasn't legitimately grown too large for
your disks?
--
Bill Moran
Collaborative Fusion Inc.
http://people.collaborativefusion.co
Or you could follow the download links on the home page.
--
Bill Moran
Collaborative Fusion Inc.
http://people.collaborativefusion.com/~wmoran/
[EMAIL PROTECTED]
Phone: 412-422-3463x4023
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http:/
a lot of improvements. If you can
spare some downtime, I highly recommend you upgrade to 8.2.7. This is
a bit more work though, because you'll have to dump your database, then
reinstall PG, then restore the data into a freshly created cluster.
In any event, make sure you have a good
UPDATE RESTRICT ON DELETE RESTRICT
> );
> -- Indexes
> CREATE INDEX akh_testing_result_testing_conf ON akh_testing_result USING
> btree (testing_conf_id);
> -- Owner
> ALTER TABLE public.akh_testing_result OWNER TO postgres;
>
>
>
>
>
>
--
Bill Moran
Collaborative Fusion Inc.
http
8.3 is fussier about type matching than 8.2 was. The query above is
casting idmovimientos to TEXT to do the comparison (since LIKE is
pointless on a BIGINT value). 8.3 doesn't do this automatically.
If you have a legit reason to do the above comparison, cast that column
to TEXT. Although I
s already broken
before you give it to pg_query().
In any event, it's unlikely that this is a bug in PostgreSQL. If you
can provide a reproducible test case, it's probably a bug in PHP.
--
Bill Moran
Collaborative Fusion Inc.
http://people.collaborativefusion.com/~wmoran/
[EMAIL
believe the problem is that you want -c, not -C (case is important).
And it should fail on 8.2 as well, the documentation lists the option
as -c and a quick test here shows similar behaviour if I use -C on
8.2.
--
Bill Moran
Collaborative Fusion Inc.
http://people.collaborativefusion.com/~wmoran/
ry conservative:
http://www.postgresql.org/docs/8.1/static/runtime-config-autovacuum.html
Additionally, you're missing 8 bug fixes in your version, I highly
recommend updating to 8.1.10 immediately.
--
Bill Moran
Collaborative Fusion Inc.
http://people.collaborativef
Magnus Hagander <[EMAIL PROTECTED]> wrote:
>
> Bill Moran wrote:
> > "Usama Dar" <[EMAIL PROTECTED]> wrote:
> >> On Dec 30, 2007 3:51 AM, Bozhan <[EMAIL PROTECTED]> wrote:
> >>
> >>>
> >>> postgres needs icon i
running or not?
I can, however, see it being a nice addition for someone who's running PG
on their desktop as part of a development environment.
In any case, I doubt it deserves to be part of PostgreSQL proper. If
someone is interested, probably a pgfoundry project would make s
In response to Alvaro Herrera <[EMAIL PROTECTED]>:
> Bill Moran wrote:
> > In response to Tom Lane <[EMAIL PROTECTED]>:
> >
> > > "Bill Moran" <[EMAIL PROTECTED]> writes:
> > > > Issuing a statement like:
> > > > CREATE
In response to Tom Lane <[EMAIL PROTECTED]>:
> "Bill Moran" <[EMAIL PROTECTED]> writes:
> > Issuing a statement like:
> > CREATE TABLE table2 AS SELECT * FROM table1;
> > simultaneously in two separate sessions should result in an error like
> > &
The following bug has been logged online:
Bug reference: 3692
Logged by: Bill Moran
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.2.5
Operating system: FreeBSD
Description:Conflicting create table statements throw unexpected
error
Details:
(also occurs on
20 matches
Mail list logo
