On Aug 3, 11:17 pm, [EMAIL PROTECTED] (Karl Denninger) wrote:
> Ideas?
SELECT item.user, item.subject, item.number
FROM item, seen
WHERE item.user = seen.user
AND item.number = seen.number
AND item.changed > seen.lastviewed
UNION
SELECT item.user, item.subject, item.number
FROM item, se
Assume the following tables:
Table ITEM (user text, subject text, number integer, changed timestamp);
table SEEN (user text, number integer, lastviewed timestamp);
Ok, now the data in the "SEEN" table will have one tuple for each user
and number in the table ITEM which a user has viewed, and th
On Friday 03 August 2007 10:04:27 Devrim GÜNDÜZ wrote:
> Complain to Reinhard, he is CC'ed to this e-mail.
>
> ftp://ftp.suse.com/pub/projects/postgresql/
>
> has only 8.2.0...
>
> BTW, I have promised to build SuSE RPMs some time ago; however Reinhard
> said that they will keep the packages up2dat
OK, as far as I saw you never mentioned what PG version you are running,
but if it's 8.2.x then I think I know what's going on. The thing that
was bothering me was the discrepancy in size of the two indexes. Now
the entries in pg_shdepend_reference_index are all going to be
references to roles, a
Does PostgreSQL support a Virtual Database like Oracle?
--Farhan
___
Yahoo! Mail is the world's favourite email. Don't settle for less, sign up for
your free account today
http://uk.rd.yahoo.com/evt=44106/*http://uk.docs.yahoo.
On Wed, 2007-08-01 at 20:41 -0600, Josh Tolley wrote:
> So please respond, if you feel so inclined, describing things you like
> to monitor in your PostgreSQL instances as well as things you would
> like to be able to easily monitor in a more ideal world. Many thanks,
> and apologies for any breach
Michael Fuhr <[EMAIL PROTECTED]> writes:
> On Thu, Aug 02, 2007 at 10:40:24PM -0400, Joseph S wrote:
>> I do use autovac. Like I said they don't get really out of hand, only
>> up to 20 megs or so before I noticed that it was weird. The large
>> indexes are what tipped me off that something str
Hello,
I've got following two-tables events queue implementation
(general idea is that multiple writers put events, while multiple readers
retrieve and handle them in order):
Table events:
ev_id: SERIAL
ev_data: bytea -- serialized event details
Table eventsconsumers:
con_name: text UNIQUE -- c
David Fetter wrote:
On Fri, Aug 03, 2007 at 09:25:41AM +0200, [EMAIL PROTECTED] wrote:
Am Donnerstag, 2. August 2007 22:37 schrieben Sie:
On Thu, Aug 02, 2007 at 11:58:40AM +0200, [EMAIL PROTECTED] wrote:
Hi,
i would like to use a statement replication for postgresql
Why?
i have read
http:/
On 8/3/07, Sergey Moroz <[EMAIL PROTECTED]> wrote:
> No that is not I meant. The problem in Prepared statements is in that you
> should determine SQL inside the function. I want to pass a query as a
> parameter, as well as query parameters.
> For example (I want to create a function like the follow
On Fri, Aug 03, 2007 at 09:25:41AM +0200, [EMAIL PROTECTED] wrote:
> Am Donnerstag, 2. August 2007 22:37 schrieben Sie:
> > On Thu, Aug 02, 2007 at 11:58:40AM +0200, [EMAIL PROTECTED] wrote:
> > > Hi,
> > >
> > > i would like to use a statement replication for postgresql
> >
> > Why?
>
> i have re
Tom Lane wrote:
Joseph S <[EMAIL PROTECTED]> writes:
... and when I notice that the tuplesperpage for the indexes is low (or
that the indexes are bigger then the tables themselves) I know it is
time for a VACUUM FULL and REINDEX on that table.
If you are taking the latter as a blind must-be-w
"Tom Lane" <[EMAIL PROTECTED]> writes:
> Ow Mun Heng <[EMAIL PROTECTED]> writes:
>> Can anyone shed some light on this. I just would like to know if queries
>> for raw data (not aggregregates) is expected to take a long time.
>> Running times between 30 - 2 hours for large dataset pulls.
>
>> Invo
On Fri, 2007-08-03 at 15:12 +0800, Ow Mun Heng wrote:
> Is 30min - 2hours too long or is this considered "normal"??
Yes.
--
Simon Riggs
EnterpriseDB http://www.enterprisedb.com
---(end of broadcast)---
TIP 6: explain analyze is your friend
Hi,
Tom Lane wrote:
Hm, looks suspiciously ASCII-like. If you examine the page as text,
is it recognizable?
Doh! Yup, is recognizable. It looks like some PHP serialized output:
png%";i:84;s:24:"%InfoToolIconActive.png%";i:85;s:29:"%InfoToolIconHighlighted.png%";i:86;s:26:"%InfoToolIconInact
On Thu, Aug 02, 2007 at 10:40:24PM -0400, Joseph S wrote:
> Tom Lane wrote:
> >Heavy use of temp tables would expand pg_class, pg_type, and especially
> >pg_attribute, but as long as you have a decent vacuuming regimen (do you
> >use autovac?) they shouldn't get out of hand.
>
> I do use autovac.
Ow Mun Heng escreveu:
Can anyone shed some light on this. I just would like to know if queries
for raw data (not aggregregates) is expected to take a long time.
Running times between 30 - 2 hours for large dataset pulls.
Involves lots of joins on very large tables (min 1 millon rows each
table,
Markus Schiltknecht <[EMAIL PROTECTED]> writes:
>> Block 58591
>> -
>> Block Offset: 0x1c9be000 Offsets: Lower12858 (0x323a)
>> Block: Size 28160 Version 73Upper14900 (0x3a34)
>> LSN: logid 627535472 recof
Ow Mun Heng <[EMAIL PROTECTED]> writes:
> Can anyone shed some light on this. I just would like to know if queries
> for raw data (not aggregregates) is expected to take a long time.
> Running times between 30 - 2 hours for large dataset pulls.
> Involves lots of joins on very large tables (min 1
On 8/3/07, Ow Mun Heng <[EMAIL PROTECTED]> wrote:
> Can anyone shed some light on this. I just would like to know if queries
> for raw data (not aggregregates) is expected to take a long time.
> Running times between 30 - 2 hours for large dataset pulls.
>
> Involves lots of joins on very large tab
Hi,
On Fri, 2007-08-03 at 11:38 +0100, Chris Coleman wrote:
> Hi,
>
> Does anyone know of anywhere to get Suse 10.1 RPMs of recent (8.2 and
> 8.3) versions of postgres?
Complain to Reinhard, he is CC'ed to this e-mail.
ftp://ftp.suse.com/pub/projects/postgresql/
has only 8.2.0...
BTW, I have
Hi,
I've set up a new CentOs server with PostgreSQL 8.2.4 and initdb'ed it with
UTF-8.
Ok, and runs fine.
I have a problem with encodings, however. And mainly with the russian cyrillic
characters.
When I testdumped some dbs from the old FC / Pg 8.0.2, all Latin1, I noticed
that some of the d
Hmm.. also data such as what is the background writer currently doing, where
are we at in checkpoint segments, how close to checkpoint timeouts are we,
etc.
On 8/2/07, Alvaro Herrera <[EMAIL PROTECTED]> wrote:
>
> Josh Tolley escribió:
> > On 8/2/07, Gavin M. Roy <[EMAIL PROTECTED]> wrote:
> > > Ar
"Elena Camossi" <[EMAIL PROTECTED]> writes:
> Hi Gregory,
>
> thank you very much for you answer!
>
>>
>> > what is the default implementation for GiST index? B-Tree or R-Tree?
>> > That is, if i execute the following SQL command:
>> >
>> > CREATE index ON table USING Gist (column)
>> >
>> >
On Friday 03 August 2007 07:38:19 Chris Coleman wrote:
> Hi,
>
> Does anyone know of anywhere to get Suse 10.1 RPMs of recent (8.2 and
> 8.3) versions of postgres?
>
> The postgres website only has fredora and redhat ones listed, and using
> rpmfind.net I can only find 8.0.13 ones for 10.0.
I usua
Hi,
I'm in the unfortunate position of having "invalid page header(s) in
block 58591 of relation "pg_toast_302599". I'm well aware that the
hardware in question isn't the most reliable one. None the less, I'd
like to restore as much of the data as possible.
A pg_filedump analysis of the file
Hi,
Does anyone know of anywhere to get Suse 10.1 RPMs of recent (8.2 and
8.3) versions of postgres?
The postgres website only has fredora and redhat ones listed, and using
rpmfind.net I can only find 8.0.13 ones for 10.0.
Thanks
Chris Coleman
Chris Coleman
Prog
Hi Gregory,
thank you very much for you answer!
>
> > what is the default implementation for GiST index? B-Tree or R-Tree?
> > That is, if i execute the following SQL command:
> >
> > CREATE index ON table USING Gist (column)
> >
> > what is the type of the index that is actually built?
>
>
Am Donnerstag, 2. August 2007 22:37 schrieben Sie:
> On Thu, Aug 02, 2007 at 11:58:40AM +0200, [EMAIL PROTECTED] wrote:
> > Hi,
> >
> > i would like to use a statement replication for postgresql
>
> Why?
i have read
http://www.postgresql.org/docs/8.2/interactive/high-availability.html
i want 4 sy
Can anyone shed some light on this. I just would like to know if queries
for raw data (not aggregregates) is expected to take a long time.
Running times between 30 - 2 hours for large dataset pulls.
Involves lots of joins on very large tables (min 1 millon rows each
table, 300 columns per table)
30 matches
Mail list logo
