Hello Palle
Under oracle we generally recommended to use newer client version
against older database versions (downwards compatibility is more often
given than upwards). But I do not know what is official recommendation
for PostgreSQL.
Regards Oli
-
Hi everybody,
I have already posted this message, but nobody answered to it.
I can't imagine that I'm the first one who have this problem, so
I post it again:
I have a problem with dump / restore commands on PostgreSQL:
pg_dump doesn't care about views dependencies:
- I create a view V1
Hi all
One of our clients (sometimes I think that all freak clients come to our
ISP) is using persistent connections via PHP (pg_pconnect) to our 7.3.2
postgres database.
Randomly their scripts fails, and doing a Reload on navigator their work
fine again.
I've put debug4 on logs and I've seen
Hello
We are planning and offering a low-cost Photo-Archive in TB range. Is
there any experience available with that amount of Data (1-3 TB)?
What kind of machines (CPU, RAM)? What kind of I/O-System? What kind of
Network (100Mbit Ethernet, Fibre, etc.).
What kind of backup-system? How to backup
Hi,
i get errors restoring a 7.2.1 dump into 7.4
the commands were
Version 7.2.1: pg_dump -Ft -b dbname > filename
Version 7.4 pg_restore -d dbname filename
pg_restore: ERROR: literal carriage return found in data
HINT: Use "\r" to represent carriage return.
CONTEXT: COPY Aktionspartner, li
W liście z pią, 28-11-2003, godz. 13:51, Oli Sennhauser pisze:
> Hello
>
> We are planning and offering a low-cost Photo-Archive in TB range. Is
> there any experience available with that amount of Data (1-3 TB)?
> What kind of machines (CPU, RAM)? What kind of I/O-System? What kind of
> Networ
Hi everyboy, my first post.
I currently have PgSQL 7.3.4 install on a OS X 10.2.8 and it works fine.
I've tried to install the new version (7.4) but each time I try to
compile it, it make me a error. I've tu upgrade th Bison parser, as says
in the warning message, but it does nothing.
I'searc
We found it!
The database host was over the firewall which had the port for postgres
opened, but the persistent connections were killed by the firewall due
to timeouts.
:D
Daniel Rubio wrote:
Hi all
One of our clients (sometimes I think that all freak clients come to our
ISP) is using persis
OK, my baseline tables are a states table, from commonly available
sources, and cities, from the Census. \d's are:
cal=# \d states
Table "public.states"
Column |Type | Modifiers
Sorry for the misleading subject. typing pgsql when I mean psql
is an unfortunate muscle memory. Happens to me in the shell, too.
Also, sorry to reply to my own post.
-j
--
Jamie Lawrence[EMAIL PROTECTED]
I'll see your senator, and I'll raise you two ju
__
Do you Yahoo!?
Free Pop-Up Blocker - Get it now
http://companion.yahoo.com/
---(end of broadcast)---
TIP 2: you can get off all lists at once with the unregister command
(send "unregister YourEmailAddressHe
Palle Girgensohn <[EMAIL PROTECTED]> writes:
> Surely, I can use an postgresql 7.2 client to connect to a 7.3.x or 7.4
> server, right?
It will work unless the client makes now-obsolete assumptions about the
layout of the system catalogs.
As an example, a 7.2 psql will work for issuing regular u
Jamie Lawrence <[EMAIL PROTECTED]> writes:
> cal=# select * from states, cities;
> server sent binary data ("B" message) without prior row description ("T" message)
Before 7.4, the client-side libpq library tended to go nuts like this
if the received query result overran available memory.
When I try to install postgres 7.3 on redhat8.0 I get into conflict problems
During the installation of the server.
It complains that it needs glibc2.3 but redhat 8.0 comes with glibc 2.2.93.
I don't want to update my glibc libraries to avoid conflicts with other
programs.
In the meanwhile I downl
I'm storing images and files in the database. I have a database server
with all of the binaries and several web servers that attach to it.
The web servers are for load balancing and each maintain a cache of
image files locally. It is the cached images that are served by the
web servers. Whe
Hi,
I am using postgres 7.0.3,
pg_dump,pg_restore version 7.2.1
I have database with lo type column
while restoring i get following message
NOTICE: DefineType: attribute "storage" not
recognized
The data restore is proper,except for the blob field
if use lo_export to extract the blob its say t
Hi,
i get errors restoring a 7.2.1 dump into 7.4
the commands were
Version 7.2.1: pg_dump -Ft -b dbname > filename
Version 7.4 pg_restore -d dbname filename
pg_restore: ERROR: literal carriage return found in data
HINT: Use "\r" to represent carriage return.
CONTEXT: COPY Aktionspartner, li
Hi!
Just a quickie:
Surely, I can use an postgresql 7.2 client to connect to a 7.3.x or 7.4
server, right? Or are there any changes made between 7.2 and higher that
will make older clients fail?
Regard,
Palle
---(end of broadcast)---
TIP 3: if po
Hello pgsql-admin,
Ppl, Hi!
I recently find, that \df+ my_function in psql, shows the whole
source code of function to user with any access rights.. this is
very harmful :( .
Does any body know are there any possibility to hide function
description (i.e. source code of plpgsql functio
thanks very much
> Hello
>
> We are planning and offering a low-cost Photo-Archive in TB range. Is
> there any experience available with that amount of Data (1-3 TB)?
> What kind of machines (CPU, RAM)? What kind of I/O-System? What kind of
> Network (100Mbit Ethernet, Fibre, etc.).
> What kind of backup-system
omkar prabhu <[EMAIL PROTECTED]> writes:
> I am using postgres 7.0.3,
> pg_dump,pg_restore version 7.2.1
You can't use a newer pg_dump/pg_restore to restore into an older server.
7.0.3 is ancient history anyway; you should update.
regards, tom lane
--
"Alexander S. Evdokimov" <[EMAIL PROTECTED]> writes:
> Does any body know are there any possibility to hide function
> description (i.e. source code of plpgsql function) from users?
No.
You could perhaps convert the function into C if you want to obfuscate
it.
regards
Thank you!
I would like to hear about any issues related to erserver. I was a
little concerned about its use of Java. Java is a great tool for
creating application frameworks for the payroll department, but using it
for back-end system-level application programming is a bit unnerving.
Java is generally s
Hi,
Hypothetical situation: a table containing, say, 10 billion rows is backed up
and then restored with pg_restore. Would this lead to the transaction id
wraparound issue since 10B rows are imported in one "batch"?
Thanks
__
Do you Yahoo!?
Free Pop-Up Blocker
ow <[EMAIL PROTECTED]> writes:
> Hypothetical situation: a table containing, say, 10 billion rows is backed up
> and then restored with pg_restore. Would this lead to the transaction id
> wraparound issue since 10B rows are imported in one "batch"?
No, because it'd only be one transaction.
Hi Armel,
I have searched hi and low on the net to try to get answers regarding
pg_dump and pg_restore, specifically to be allow them to run with crontab on
the red hat servers that I look after as programmer and general IT dogs
body. I would appear from the general brevity of the replys ; that
On Sun, Nov 23, 2003 at 10:51:10PM -0500, Anjan Dave wrote:
> Hi All:
>
> I am trying to restore a database on a different machine (7.2.3 on Sol9 to 7.2.4
> RH8), and i get the following error, that i haven't seen before:
>
> -bash-2.05b$ pg_restore -d access -Ft -a access.dump.tar
> pg_restor
Hello,
Did the dump come from those machines? If so, it is probably not a valid
archive anyway because you hit the 2gig limit. My suggestion would be to
recompile PostgreSQL with the 64bit file access.
Sincerely,
Joshua D. Drake
Kurt Roeckx wrote:
On Sun, Nov 23, 2003 at 10:51:10PM -0500, Anj
Something very important was recently raised on the [EMAIL PROTECTED]
list. Due to the current environment that SCO is fostering in the
open source community, it would be prudent for the PostgreSQL team to
consider this issue.
The website claims that "PostgreSQL is distributed under the flexible
Breen Ouellette <[EMAIL PROTECTED]> writes:
> The result of this ambiguity is that the
> latest CD release of OpenBSD (3.4) no longer includes Postgresql
We are not changing the license text we inherited from Berkeley.
We do not have the right to, nor any interest in doing so.
Our interpretation
Tom Lane wrote:
> Breen Ouellette <[EMAIL PROTECTED]> writes:
> > The result of this ambiguity is that the
> > latest CD release of OpenBSD (3.4) no longer includes Postgresql
>
> We are not changing the license text we inherited from Berkeley.
> We do not have the right to, nor any interest in do
Richard Welty wrote:
> but you can consult with the attorneys for the Regents. they have
> changed the license at times, and have passed those changes on
> to other BSD licensed projects (e.g., when they removed the
> advertising clause the advertising clause was also removed from
> all the code in
Richard Welty wrote:
> On Fri, 28 Nov 2003 17:23:56 -0500 (EST) Bruce Momjian <[EMAIL PROTECTED]> wrote:
>
> > Richard Welty wrote:
> > > but you can consult with the attorneys for the Regents. they have
> > > changed the license at times, and have passed those changes on
> > > to other BSD licens
Richard Welty wrote:
> On Fri, 28 Nov 2003 17:58:19 -0500 (EST) Bruce Momjian <[EMAIL PROTECTED]> wrote:
> > OK, where did you get this wording? Is this something Berkeley released
> > as one of their versions of the BSD license.
>
> yes, i believe that it originally came from the Berkeley lawyer
36 matches
Mail list logo
