> -Original Message-
> From: Tom Lane [mailto:[EMAIL PROTECTED]
> Sent: 10 July 2003 17:07
> To: Dave Page
> Cc: Donald Fraser; [ADMIN]; [pgADMIN]
> Subject: Re: [ADMIN] [pgadmin-support] Overloading functions
> that are used by operators.
>
>
> "Dave Page" <[EMAIL PROTECTED]> writes
A man walks ito a doctor's office, and he says, "Doctor, it hurts when I do this."
The doctor says, "Don't do that."
"T.J. Hoo" wrote:
> Hi!
>
> I don't want to use PostgreSQL "the Unix way" on Windows and so I did not
> install the Cygwin and tried to compile using Microsoft Visual C++ 6.0.
news.us.postgresql.org is up right now, and gatewaying ...
news.postgresql.org will come back online as soon as I'm able to get some
more hardware online handle it, which we're just getting ready to ship out
... message pointesr will be out of sync, unfortunately, so altho we are
adding redundancy
On Fri, 2003-07-18 at 13:26, Naomi Walker wrote:
> I noticed in some (older) documentation that views were read-only? Is this
> still the case?
Yes, views are read-only unless you define rules for how they can be
inserted/updated/deleted from.
See these for how to create those rules:
http://dev
Yep. by default views are not updateable in postgresql. However, they
can be made updateable by triggers. Note that not all views are
inherently updateable, just the simplest. for instance how would you
update:
create view bigview as select g1.id, t1.f1*t2.f2, t1.f3/t3.f4 from tabl1
t1, ta
Title: Message
So I have a "data/base/myDB/" directory with a database that I need to
restore from Postgres 7.0.2 on a
Cobalt RaQ4 that went down. All I have is the
directory to work with, and I see these files that I need are in there. I opened
up one of the table files with a text editor
I noticed in some (older) documentation that views were read-only? Is this
still the case?
Naomi
-
Naomi Walker Chief Information Officer
All PostgreSQL can be run under Cygwin.
---
Marvin wrote:
>
> Ok Thank you,
> I will try to install it on my machine.
> Do you know what version of Postgres is using this Cygwin?
>
> Regards,
>
> Mago
>
> ---Mensaje
Ok Thank you,
I will try to install it on my machine.
Do you know what version of Postgres is using this Cygwin?
Regards,
Mago
---Mensaje original---
De: Bruce Momjian
Fecha: Viernes, 18 de Julio de 2003 09:03:52 a.m.
A: Marvin
CC: [EMAIL PROTECTED]
Asunto: Re: [ADMIN] UltraS
No more recent version of UltraSQL, but you can use Cygwin with
PostgreSQL. We are working on a native Win32, but that is a few months
away.
---
Marvin wrote:
> I'm currently using "PostgreSQL 7.2.1 on i686-pc-winnt-msdev,
Hello,
The link http://www.ca.postgresql.org/docs/momjian/upgrade_tips_7.3 is no
longer valid.
Where i can found this tips?
Thanks,
Sergio Pili
---(end of broadcast)---
TIP 9: the planner will ignore your desire to choose an index scan if your
On Thu, 17 Jul 2003, mlaks wrote:
> Hi,
>
> I have about 15 different PC's running RedHat 7.3 Linux, each running the
> same database backed application (I use Postgresql 7.2.1 for the database)
> on each machine.
Upgrade to 7.2.4 as soon as possible. There are bugs in 7.2.3 and before
th
Andreas Schmitz <[EMAIL PROTECTED]> writes:
> I did a vacuum full and analyze but this pg_temp namespaces are still there.
> Any ideas about that phenomena ?
They're supposed to be there; we recycle the pg_namespace entry across
successive backend sessions. I see no point in deleting it only to
I'm currently using "PostgreSQL 7.2.1 on i686-pc-winnt-msdev, compiled by msdev 6.0" version that I found in postgresql site. This is the PeerDirect UltraSQL version for Windows. However I would like to know if there is a more recent version because I need to use the 7.4.
Any suggestions?
On Thu, Jul 17, 2003 at 10:32:24PM -0400, mlaks wrote:
> Hi,
>
> I have about 15 different PC's running RedHat 7.3 Linux, each running the
> same database backed application (I use Postgresql 7.2.1 for the database)
Upgrade that to 7.2.4, at least. Noo need to dump and restore, but
you get s
Hello *,
we started the use of temporary tables for evaluating data.
create temp table xxx
drop temp table xxx;
We encountered some strange errors about relation exists or even does not
exist from server and application site. I started to look after orphan temp
tables. No orphans wer
Tom Lane wrote:
Sergio Pili <[EMAIL PROTECTED]> writes:
pg_dump abort with this error:
pg_dump: dumpBlobs(): error reading large object: ERROR: cannot read block
6389 of pg_largeobject_loid_pn_index: Input/output error
This error is caused by bad block on my hard drive?
Looks lik
"mlaks" <[EMAIL PROTECTED]> wrote:
> But I run vaccuum analyze at the same frequency as on the PC's? How is it
that
> deleting and saving and vacuum analyze doesnt keep it at a normal svelte
<1Gb
> in size?
>
> What should I do to shrink it back down to its normal svelte shape?
Did you try to vac
18 matches
Mail list logo
