On Mittwoch, 13. Mai 2009, Alvaro Herrera wrote:
> > we're using postgresql 8.3 for some logging framework.
> >
> > There are several tables for each day (which are inherited from a common
> > base), which
> > - are filled during the day,
> > - after midnight the indizes are changed to FILLFACTOR=1
On Mon, 20 Apr 2009, Jan Otto wrote:
If you have big toast tables you get wrong results with the query suggested
at http://wiki.postgresql.org/wiki/Disk_Usage because it takes the toasted
values not into account.
I can't recall why I wrote that to filter out things in the pg_toast
namespace i
Shahbaz A. Tyagi wrote:
Hi,
Its not happening in all the machines, its only some machines. I am testing
on XP 32 bit. Its coming only while running Postgres and accessing the DB.
Strange part is that some machines are getting restarted as soon as it gets
the error.
You mean the whole machine
AntiVirus is not running.
-Original Message-
From: pgsql-general-ow...@postgresql.org
[mailto:pgsql-general-ow...@postgresql.org] On Behalf Of Scott Marlowe
Sent: Thursday, May 14, 2009 3:35 AM
To: Shahbaz A. Tyagi
Cc: Richard Huxton; pgsql-general@postgresql.org
Subject: Re: [GENERAL
in the psql prompt try this:
\! stty sane
Ing. Edmundo Robles Lopez.
Analista Programador.
--
-Original Message-
From: pgsql-general-ow...@postgresql.org on behalf of Juan Camilo Marín
Sent: Wed 5/13/2009 12:58 PM
To: Craig Ringer
Cc: pgsql-general@postgresql.org
Subject: Re: [GENER
I tried the pgInstaller instead of the One Click Installer and
everything installed correctly.
Andrew
On Thu, May 14, 2009 at 10:34 AM, Andrew Maclean
wrote:
> I did a fresh installation after deleting every reference to postgres
> and pgAdmin in the registry and removing the relevant folders.
I did a fresh installation after deleting every reference to postgres
and pgAdmin in the registry and removing the relevant folders.
It looks as if the installation fails when loading additional modules.
I also think host should be localhost at this stage.
Here is a portion of the log that shows a
I used pg_dump to extract the data from my database with bytea fields
(having pictures) in plain text format. I encoutered some problems to
restore those bytea data to the blobs field in a Mysql database. Any advice?
Hi All,
Let's consider the following case: WAL segments from a master have
been shipped to N warm standby servers, and now the master fails.
Using this or that mechanism, one of the warm standbys takes over and
becomes the new master. Now the question is what to do with the other
N-1 warm st
I'll check this out but I am puzzled as to why it suddenly appeared after
upgrading.
-Original Message-
From: Scott Marlowe [mailto:scott.marl...@gmail.com]
Sent: Thursday, 14 May 2009 09:40
To: a.macl...@cas.edu.au
Cc: General
Subject: Re: [GENERAL] postgres 3.7 unexpected closing of co
Actually it is happening on two different Vista platforms one running McAfee
and the other Symantec.
Andrew
-Original Message-
From: Scott Marlowe [mailto:scott.marl...@gmail.com]
Sent: Thursday, 14 May 2009 09:40
To: a.macl...@cas.edu.au
Cc: General
Subject: Re: [GENERAL] postgres 3.7 u
On Wed, May 13, 2009 at 5:36 PM, Andrew Maclean
wrote:
> I have the following error message:
>
> "Error connecting to the server: server closed the connection unexpectedly.
> This probably means that the server terminated abnormally before or
> while processing the request.
> "
> It happens inter
I have the following error message:
"Error connecting to the server: server closed the connection unexpectedly.
This probably means that the server terminated abnormally before or
while processing the request.
"
It happens intermittently both when using pgAdminIII and when using QT
so it is not a
On Wed, May 13, 2009 at 4:22 PM, Shahbaz A. Tyagi
wrote:
> Hi,
>
> Its not happening in all the machines, its only some machines. I am testing
> on XP 32 bit. Its coming only while running Postgres and accessing the DB.
>
> Strange part is that some machines are getting restarted as soon as it get
Hi,
Its not happening in all the machines, its only some machines. I am testing
on XP 32 bit. Its coming only while running Postgres and accessing the DB.
Strange part is that some machines are getting restarted as soon as it gets
the error.
Thanks,
-Original Message-
From: pgsql-gen
Shahbaz A. Tyagi wrote:
We are using Postgres 8.3.1 binary distribution, and copying the same along
with software installation.
Can you reproduce this with a more recent version of 8.3 (8.3.7 is current).
From last some time we have started getting error as message dialog showing
error 0xC000
On 13/05/2009 21:56, George Kao wrote:
> I used pg_dump to extract the data from my database with bytea fields
> (having pictures) in plain text format. I encoutered some problems to
> restore those bytea data to the blobs field in a Mysql database. Any advice?
A bit more detail would be nice
Hi,
We are using Postgres 8.3.1 binary distribution, and copying the same along
with software installation.
>From last some time we have started getting error as message dialog showing
error 0xC142 and after that, connections are crashing.
Windows login is administrator user and Pos
Who many thanks Laurenz.
You gave me the right direction.
The following is what I made up and it does exactly what I want it to do:
--collect the specific string data for each result row
SELECT (
SELECT match[1] FROM
regexp_matches(secondresult.imgstring,'title="([^"]+)"','ig') AS
Michael P. Soulier wrote:
> So, I'm working around it by creating the new columns with the default
> value that I want populated, and then resetting the default. This works,
> but it doesn't feel like a best practice.
>
> Can someone recommend a better way to say, consolidate 3 columns down to
> 2
Hello Craig.
Thanks for your answer. I did what you say (use the default size of the
terminal) but the problem persist, the psql still start to write the new
senteces above the old one, it is to weird.
Best regards,
2009/5/10 Craig Ringer
> Juan Camilo Marín wrote:
>
> > => select * from \d su
Philipp Marek wrote:
> Hello everybody,
>
> we're using postgresql 8.3 for some logging framework.
>
> There are several tables for each day (which are inherited from a common
> base), which
> - are filled during the day,
> - after midnight the indizes are changed to FILLFACTOR=100, and
> - the
Jonathan Groll writes:
> Custom built postgresql 8.3.5 using the pkgsrc build system on OS X
> Leopard;
Uh ... what is the "pkgsrc build system", and what changes does it make
to a straight-from-source PG build?
> creating conversions ... ok
> creating dictionaries ... FATAL: could not access f
Hopefully this is a quick one to answer, but it's got me tearing my
hair out.
Custom built postgresql 8.3.5 using the pkgsrc build system on OS X
Leopard; when running: /usr/pkg/bin/initdb -D /usr/pkg/pgsql/data
(I also tried adding the -d flag but no other useful information was
shown)
as the
Quoting "Scott Marlowe" :
Whether or not max relations is the root of the login hang problem,
you likely have gotten a fair bit of bloat in your database if your
setting was too low by a factor of 10 for so long.You may need to
look at recovering lost space in bloated tables and / or indexes.
WP Perquin wrote:
> When I make the following simplified example:
>
> SELECT regexp_matches(''
>
> ,'((title\s*=\s*\"([^"]*)")+)|((src\s*=\s*\"([^"]*)")+)','ig')
>
> My result are 2 rows:
>
> "{NULL,NULL,NULL,"src=\"\"","src=\"\"",}"
>
> "{"title=\"dit is een title tekst\"","title=
On Wed, May 13, 2009 at 1:42 AM, Henry wrote:
> Quoting "Thomas Markus" :
>>
>> check your hardware (especially harddrive) for errors.
>
> Ja, that was my first suspicion as well, but no. Using a RAID5 setup, with
> smart monitoring, etc ... no errors.
>
> I've also just bumped up max_fsm_relatio
Quoting "Thomas Markus" :
check your hardware (especially harddrive) for errors.
Ja, that was my first suspicion as well, but no. Using a RAID5 setup,
with smart monitoring, etc ... no errors.
I've also just bumped up max_fsm_relations to 1 - it was using the
default of 1000 or somet
28 matches
Mail list logo
