I'm trying to install PG9.1 on RHEL5 and I have some problems with
it.
Currently there is some old version of PG90 installed but
theoretically 90 & 91 should cohabit together without any problems.
yum list postgresql*
-
I would love to say it solves my problem, but it really don't ;)
> wstrzalka wrote:
> > Hi
>
> > Is there any estimate where 9.1 potentially could be released?
>
> Sure. When it's ready ;-)
>
> Andreas
> --
> Really, I'm not out t
Hi
Is there any estimate where 9.1 potentially could be released?
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
On 26 Aug, 01:28, pie...@hogranch.com (John R Pierce) wrote:
> On 08/25/10 11:47 AM, Wojciech Strzałka wrote:
>
> > The data set is 9mln rows - about 250 columns
>
> Having 250 columns in a single table sets off the 'normalization' alarm
> in my head.
>
> --
> Sent via pgsql-general mailing lis
On 26 Sie, 08:06, wstrzalka wrote:
> On 26 Aug, 01:28, pie...@hogranch.com (John R Pierce) wrote:
>
> > On 08/25/10 11:47 AM, Wojciech Strzałka wrote:
>
> > > The data set is 9mln rows - about 250 columns
>
> > Having 250 columns in a single table sets off th
I'm currently playing with very large data import using COPY from
file.
As this can be extremely long operation (hours in my case) the nice
feature would be some option to show operation progress - how many
rows were already imported.
Or maybe there is some way to do it? As long as postgres have
So the query is:
SELECT m.messageid, mad.destination
FROM messages AS m
LEFT JOIN message_address_link AS mal ON (mal.message_id =
m.messageid)
JOIN message_address_data AS mad ON (mad.id = mal.address_id)
WHERE delete_status <> 1
AND folderid=E'200702210742181172061738846603
Hi
This is probably more like linux question but strictly related to
PG so I hope somebody can help me.
I need to have 8.3 & 8.4 installed on the same machine (for
pg_migrator). As I'm not Linux guru I used to install/update Postgres
using yum from PGDG.
Is there any clever way to insta
Why PG sort's my data in case insensitive manner?
masterdb=# SELECT name FROM enterprises ORDER BY name;
name
--
abc
AKS 514
aks518
AKSFree1
..
The worst (totally mess) example is:
masterdb=# S
It's kind of lame questions, possibly I'm missing something but my
doubts are as follow:
When planner/executor needs to sort rowsit sorts whole records (i
think so). So in the case when there are many wide columns it takes
quite a lot of memory and sort goes out to the disk because it excess
the w
> - EXPLAIN does not work with functions.
+1
and one more about explain - it would be great to have smth like:
EXPLAIN ANALYZE FULL - that would show details about the plan chosen
with detailed explanation and other plans considered.
It would reduce a few posts a week in style:
- 'why the query A
On Feb 2, 8:23 pm, br...@momjian.us (Bruce Momjian) wrote:
> wstrzalka wrote:
> > * stat collector is really greedy by definition even when system is
> > idle, when you have really really many relations
>
> I think this will be fixed in 8.4.
>
That would by great
My short list is:
* in-place upgrade
* named parameters in SQL functions
* native jobs
* timestamptz that preserves original timezone (not offset but
political timezone like America/New_York)
* I hate: "select * from dblink(...) as WHY(I_NEED int4, TO_SPECIFY
int4, THIS text)"
* ability to c
http://www.postgresqlcertification.org/jta/2008/results
Having point 4 as an example:
For how long have you been a PostgreSQL database administrator?
Less than 1 year36
I wish.
Messed up - I mean when going "up" and scrolling command history it
shows long queries (eg 2 line long) in single line and the exceeding
part overwrites the beginning of the query), or when writing long SQL
at some point I'm starting to overwriting it from the beginning of the
line.
Sometimes whe
On 27 Paź, 13:16, [EMAIL PROTECTED] (Sam Mason) wrote:
> On Mon, Oct 27, 2008 at 01:59:42AM -0700, wstrzalka wrote:
> > I'm using psql mainly in putty window.
>
> it's pretty much always just worked with me. I'm using a very old
> version of putty, but it all h
I'm using psql mainly in putty window.
I have a problem while resizing the window.
When changing the window size (and those chars per row) psql output
becomes mess, the only rescue is to exit and run the psql again. It
looks like it's initializing the output params at startup and don't
refresh it
This is top of my 'top':
15483 postgres 15 0 147m 31m 284 R 17 0.8 29033:23 postgres
24599 postgres 15 0 1293m 274m 231m S2 6.9 0:02.05 postgres
24598 postgres 15 0 1258m 99m 88m S1 2.5 0:00.62 postgres
the 15483 process is stats collector. At the moment server is
Is there any possibility to have reverse() function in the PG core in
the future?
There are some implementation already like ie. this one:
http://blog.frosties.org/post/2007/08/28/Fonction-reverse-C-avec-PostgreSQL
I think author will have nothing against using his code as he
published it on his
On 29 Kwi, 17:16, [EMAIL PROTECTED] (Erik Jones) wrote:
> On Apr 29, 2008, at 3:20 AM, wstrzalka wrote:
>
>
>
> >> What is the full pg_standby command string (restore_command=) in
> >> your recovery.conf. It sound's like you have pg_standby set to
> >
> What is the full pg_standby command string (restore_command=) in
> your recovery.conf. It sound's like you have pg_standby set to delete
> archived WALs and possibly have that a little too aggressive. Do you
> have the -k flag set in your pg_standby call in your restore_command?
My restore
I have some problem with setting up PITR recovery on the database.
I have archive_command set properly and logs are shipping OK. Archive
timeout is also set (5 min).
When performing pg_start_backup the WAL is lets say on position
0001000100D9, then I start copy database to the second
I've just realized that I can call pg_switch_xlog() from cron or
pgAgent instead of using archive_timeout, but the question is still
open. Doing it internally in PG would be much more elegant.
Thanks
Wojtek Strzalka
--
Sent via
I have a question if it is possible that having archive_timeout set up
it will behave like pg_switch_xlog() in the term of non creating new
WAL when there are no changes in the database.
archive_timeout is used for WAL shipping to standby server in my case
(are there any other reasons?), but WAL i
On 23 Kwi, 16:32, [EMAIL PROTECTED] (Tom Lane) wrote:
> Alvaro Herrera <[EMAIL PROTECTED]> writes:
> > I think this business of non-shortcircuiting boolean operators is just
> > an artifact of the fact that PL/pgSQL hands off expression to the SQL
> > engine for evaluation.
>
> The complainant is n
One of the annoying things in plpgsql is logical expression
evaluation.
In most (all??) languages I know, logical expression like:
if ( [A_true_expression] or [B_false_expression] ) then
will stop evaluating when the A expression will be evaluated as a
TRUE.
So the B will be not checked. In
Hi
Features like CREATE DATABASE WITH TEMPLATE or CREATE TABLE LIKE
are very usefull but it would be great to have such a feature on the
mid-level too. I mean something CREATE SCHEMA LIKE that would copy all
the template schema relations, etc...
What do you think about it ? Would it be hard to
27 matches
Mail list logo
