On Mon, Feb 18, 2008 at 06:35:11PM -0300, Alvaro Herrera wrote:
Bruce Momjian escribió:
Magnus Hagander wrote:
For the case of upgrading, it wouldn't work. But there are certainly
other cases where it would help. Say from your central pgadmin console
administering 10 servers from 3
On Feb 18, 1:14 pm, pgsql_user [EMAIL PROTECTED] wrote:
On Feb 18, 6:08 pm, Paul Boddie [EMAIL PROTECTED] wrote:
On 18 Feb, 13:36, django_user [EMAIL PROTECTED] wrote:
How can stop postgresql from incrementing the primary key value, so
that even after many failed insert statements it
On Feb 19, 2008 8:48 AM, Magnus Hagander [EMAIL PROTECTED] wrote:
On Mon, Feb 18, 2008 at 06:35:11PM -0300, Alvaro Herrera wrote:
Bruce Momjian escribió:
Magnus Hagander wrote:
For the case of upgrading, it wouldn't work. But there are certainly
other cases where it would help. Say
On Tue, Feb 19, 2008 at 03:55:27PM +0600, Markus Bertheau wrote:
The toast pages are stored in a separate table - see manual for
details. There's a whole chapter (53.2) on this.
Yes, but I assume that on disk the pages will be laid out sequentially
- not intentionally so, of course. See
2008/2/19, Richard Huxton [EMAIL PROTECTED]:
Markus Bertheau wrote:
Afaics, TOAST was invented so that big attributes wouldn't be in the
way when working with the other attributes.
Actually, I think it was designed as a way of working around PG's 8KB
block-size. That imposed a maximum row
Markus Bertheau wrote:
Afaics, TOAST was invented so that big attributes wouldn't be in the
way (of readahead, the buffer cache and so on) when working with the
other attributes. This is based on the assumption that the other
attributes are accessed more often than the whole contents of the big
On Mon, Feb 18, 2008 at 05:01:22PM +, Dave Page wrote:
On Feb 18, 2008 4:52 PM, Bill Moran [EMAIL PROTECTED] wrote:
In response to [EMAIL PROTECTED] [EMAIL PROTECTED]:
Hi
My porting experiment has encountered the SQL Server UniqueIdentifier
problem. I can see one or two
Markus Bertheau wrote:
2008/2/19, Richard Huxton [EMAIL PROTECTED]:
I'm loading a table with some short attributes and a large toastable attribute.
That means that for every main table heap page several toast table heap pages
are written. This happens through the buffer cache and the background
Hello List membersI have just upgraded the PostgreSQL server from 8.2.4 to 8.3 on Suse 10.3 64 bit.While inspecting the log i see this errorERROR: shared buffer hash table corruptedCan anybody please help me in getting into details of it?With regardsAshish...
Unlimited freedom, unlimited
Hi,
I'm just wondering why lib\ms\*.lib files are not part of
binaries-no-installer distribution.
Is there any specific reason they're not included there?
regards,
josue gomes
---(end of broadcast)---
TIP 1: if posting/reading through Usenet,
Hi,
It seems the greylisting setup stopped quarantining emails? I'm getting
a lot more spam in pgsql-hackers and the other lists I moderate, and
nothing in the headers suggest that they were greylisted at all.
Did something happen?
--
Alvaro Herrera
Hi,
Thank you guys.
Enrico Sirola wrote:
Il giorno 18/feb/08, alle ore 17:37, [EMAIL PROTECTED] ha scritto:
1) PostgreSQL only support partition by inheritance, and rules have to
be created for each child table, this will result *a lot of* rules if
the number of child tables is large.
Are
I'm going to have to loook into it ... Dave just reported that also ... as
far as I know, everything should be still working, unless I somehow
disabled it the other day when I was in on the bayes stuff (not sure how,
its a screen I never visit) ...
Will investigate ...
On Tue, 19 Feb
On Feb 19, 2008 1:16 PM, Josue Gomes [EMAIL PROTECTED] wrote:
Hi,
I'm just wondering why lib\ms\*.lib files are not part of
binaries-no-installer distribution.
Is there any specific reason they're not included there?
Everything is Microsoft-compiled now, so no need for special versions
of
Joe Conway wrote:
Erik Jones wrote:
See how postgres handles filling the NULLs for you? What you'd really
want to do with this would be to define some functions for setting and
getting a person's answers to a given question or set of questions so
that you could implement some kind of
Alvaro Herrera wrote:
Joe Conway wrote:
It occurs to me that it shouldn't be terribly difficult to make an
alternate version of crosstab() that returns an array rather than tuples
(back when crosstab() was first written, Postgres didn't support NULL
array elements). Is this worth
django_user wrote:
How can stop postgresql from incrementing the primary key value, so
that even after many failed insert statements it get the next id val.
,,,
so wouldnt I run out of ids one day, if there are lot of failed insert
statements, lets say for every successful insert there are 50
Can I have something like this in my SQL text file:
(items_seq.nextval(), '', '...')
?
Raymond O'Donnell [EMAIL PROTECTED] wrote: On 19/02/2008 15:43, HHB wrote:
How to use a sequence in such text files?
You're looking for the nextval() function - look it up in the docs.
Ray.
HHB wrote:
Hi.
I have sequence for each table in my database.
In order to populate same data in the database, I created some SQL text
files.
---
insert into categories values (id value from sequence, '..', '...');
insert into books values (id value from sequence, '..', '...', '..', fk to
Hi Everyone,
Many years ago I created a domain with a char(4) datatype.
Now in my wisdom I would like to change this to a text datatype, but I can't
see any way of altering the type of a domain.
I have experimented with backing up the database and manually editing the
dump file to change
On Feb 19, 2008, at 7:46 AM, [EMAIL PROTECTED] wrote:
I have tried to do partition with inheritance and rules. First, I
created master table and many child table, and also the rules for
insert, delete and update. Then I do some select, insert, delete
and update operations on the master to
2008/2/19, Richard Huxton [EMAIL PROTECTED]:
Markus Bertheau wrote:
2008/2/19, Richard Huxton [EMAIL PROTECTED]:
I'm loading a table with some short attributes and a large toastable
attribute.
That means that for every main table heap page several toast table heap
pages
are written.
Hi.
I have sequence for each table in my database.
In order to populate same data in the database, I created some SQL text
files.
---
insert into categories values (id value from sequence, '..', '...');
insert into books values (id value from sequence, '..', '...', '..', fk to
category id);
---
On 19/02/2008 15:43, HHB wrote:
How to use a sequence in such text files?
You're looking for the nextval() function - look it up in the docs.
Ray.
---
Raymond O'Donnell, Director of Music, Galway Cathedral, Ireland
[EMAIL
Magnus Hagander [EMAIL PROTECTED] writes:
Lack of support for Windows, which it sounds like the OP might be running?
That's something that's been on my agenda for a while. There are certainly
UUID generation functions available on Windows - at least for some of the
cases supported by
HHB wrote:
Hi.
I have sequence for each table in my database.
In order to populate same data in the database, I created some SQL text
files.
---
insert into categories values (id value from sequence, '..', '...');
insert into books values (id value from sequence, '..', '...', '..', fk to
On Tue, Feb 19, 2008 at 11:56:08AM -0300, Alvaro Herrera wrote:
Joe Conway wrote:
Erik Jones wrote:
See how postgres handles filling the NULLs for you? What you'd
really want to do with this would be to define some functions
for setting and getting a person's answers to a given
It occurs to me that it shouldn't be terribly difficult to make an
alternate version of crosstab() that returns an array rather than
tuples (back when crosstab() was first written, Postgres didn't
support NULL array elements). Is this worth considering for 8.4?
How about
On Feb 19, 2008 6:33 PM, Josue Gomes [EMAIL PROTECTED] wrote:
On 2/19/08, Dave Page [EMAIL PROTECTED] wrote:
On Feb 19, 2008 1:16 PM, Josue Gomes [EMAIL PROTECTED] wrote:
Hi,
I'm just wondering why lib\ms\*.lib files are not part of
binaries-no-installer distribution.
Is there
It turned out that NT Authority\Authenticated Users and NT Authority
\Interactive had been removed from the Users group on the machine that
was getting the initdb permission error. Added these back to the
Users group and the install was successful.
---(end of
On Tue, 2008-02-19 at 11:07 -0500, Tom Lane wrote:
Magnus Hagander [EMAIL PROTECTED] writes:
Lack of support for Windows, which it sounds like the OP might be running?
That's something that's been on my agenda for a while. There are certainly
UUID generation functions available on
Magnus Hagander wrote:
On Tue, 2008-02-19 at 11:07 -0500, Tom Lane wrote:
Why can't ossp be used --- is it impossible to port to Windows?
I haven't looked into the details - it's possible that it could be
portable to Windows. But that would a Yet Another Dependency to be bale
to build
hi
when i try to uninstall tsearch2 i get this error,
my postgres version is 8.2.5
how to fix this?
thanks a lot!
/usr/local/pgsql/bin/psql -U postgres -h localhost -f
/usr/local/pgsql/share/contrib/uninstall_tsearch2.sql
BEGIN
psql:/usr/local/pgsql/share/contrib/uninstall_tsearch2.sql:8:
[EMAIL PROTECTED] [EMAIL PROTECTED] writes:
when i try to uninstall tsearch2 i get this error,
Hmm, maybe you originally put tsearch2 into some other schema than
public? If so, try setting search_path to point to that schema
before you run the uninstall script.
For that matter, are you sure
We've just started seeing these errors. Research I've done seems to
indicate that it's related to temp tables. Question is, we didn't start
seeing these errors until we started using slony to replicate our data.
The errors only showed up shortly after the initial replication of the
data was
Post the table, the query, and the explain output, and then we can help you.
On Feb 19, 2008 7:38 PM, hewei [EMAIL PROTECTED] wrote:
Hi,Every body;
I have a table contains 100,000 rows, and has a primary key(int).
Now ,I need to execute sql command like update .. where id=*(id
is
table:
CREATE TABLE price (
TIMESTAMP Timestamp NULL,
idnumeric(5,0) NOT NULL,
price numeric(10,3) NULL,
primary key (id)
);
sql:
update price set price=* where id=*;
On Feb 20, 2008 11:56 AM, Webb Sprague [EMAIL PROTECTED] wrote:
Post the table, the query, and the
I'm running a simple query on 8.2. With this syntax, Explain indicate
that the index is scanned:
select * from eod where name = 'AA'
However, when I change the query to use simple regex:
select * from eod where name ~ 'AA'
now Explain indicates a seq scan:
Index Scan using equity_eod_symbol_idx
Hi,Every body;
I have a table contains 100,000 rows, and has a primary key(int).
Now ,I need to execute sql command like update .. where id=*(id
is primary key).
I expect execute 1200-1600 sqlcommands per second(1200-1600/s).
In test,when the id increase by degrees in sqlcommands,
hewei [EMAIL PROTECTED] writes:
idnumeric(5,0) NOT NULL,
Don't use NUMERIC where INTEGER would do ...
regards, tom lane
---(end of broadcast)---
TIP 9: In versions below 8.0, the planner will ignore your desire to
On Feb 19, 2008, at 9:32 PM, Postgres User wrote:
I'm running a simple query on 8.2. With this syntax, Explain indicate
that the index is scanned:
select * from eod where name = 'AA'
However, when I change the query to use simple regex:
select * from eod where name ~ 'AA'
now Explain
hello list,
i am a newbie in postgresql.
i ported a small application to postgresql 8.2 originally written to store data
in maxdb. since stored procedures are not supported in postgresql and since
postgresql functions cannot return cursor to the calling applications, i
rewrote the maxdb
On Monday 04 February 2008 10:48, vincent wrote:
Christopher Browne wrote:
Personally I'm surprised that the last couple responses seem to center
around not being able to make much money off of it. I agree that it
would require some time investment, but so did building PG in the first
Thanks, my dumb mistake.
I need to perform the equivalent of a WHERE clause OR expression using
regex to match exact strings.
_
this example hits the index:
select * from eod where name ~ '^BA$'
but when I try to add
Postgres User wrote:
Yes that works, but the whole point of the exercise is replace many OR
statements with 1 regex expression. So it's not what I'm looking for.
Why do you want it done this way?
You can build an array of strings to check and use an in clause.
Using php :
$checks =
serafin segador [EMAIL PROTECTED] writes:
i ported a small application to postgresql 8.2 originally written to store
data in maxdb. since stored procedures are not supported in postgresql and
since postgresql functions cannot return cursor to the calling applications,
i rewrote the maxdb
im trying to allow the client to pass a varchar param into my
function, and want to avoid any parsing of the parameter inside the
function, or code to build a sql string.
if the function can use this code, it will be compiled and optimized
(unlike a dynamic sql stirng)
select * from mytable
Postgres User [EMAIL PROTECTED] writes:
Yes that works, but the whole point of the exercise is replace many OR
statements with 1 regex expression. So it's not what I'm looking for.
Unfortunately, Postgres is not as intelligent as you are. There is
no mechanism to rewrite a multi-branch regex
Yes that works, but the whole point of the exercise is replace many OR
statements with 1 regex expression. So it's not what I'm looking for.
On Feb 19, 2008 9:16 PM, Chris [EMAIL PROTECTED] wrote:
Postgres User wrote:
Thanks, my dumb mistake.
I need to perform the equivalent of a WHERE
Postgres User wrote:
Thanks, my dumb mistake.
I need to perform the equivalent of a WHERE clause OR expression using
regex to match exact strings.
_
this example hits the index:
select * from eod where name ~ '^BA$'
but
by the way, your example works fine unless it's a null value or empty string
unfortunately, postgres isn't smart enough to know that the when
p_param below is null, that the WHERE condition can be ignored
select * from table where name in (Coalesce(p_param, name))
which is the same as: select
Postgres User wrote:
by the way, your example works fine unless it's a null value or empty string
unfortunately, postgres isn't smart enough to know that the when
p_param below is null, that the WHERE condition can be ignored
select * from table where name in (Coalesce(p_param, name))
which is
2008/2/20, Geoffrey [EMAIL PROTECTED]:
We've just started seeing these errors. Research I've done seems to
indicate that it's related to temp tables. Question is, we didn't start
seeing these errors until we started using slony to replicate our data.
The errors only showed up shortly after
doh! tom, let me know if you decide to hack out a fix for this one of
these nights ;)
thanks for your help.
On Feb 19, 2008 9:45 PM, Tom Lane [EMAIL PROTECTED] wrote:
Postgres User [EMAIL PROTECTED] writes:
Yes that works, but the whole point of the exercise is replace many OR
statements
hello list,
i am a newbie in postgresql.
i ported a small application to postgresql 8.2 originally written to store
data in maxdb. since stored procedures are not supported in postgresql
and since postgresql functions cannot return cursor to the calling
applications, i rewrote the maxdb
On Feb 19, 2008 11:39 PM, Tom Lane [EMAIL PROTECTED] wrote:
and since postgresql functions cannot return cursor to the
calling applications,
Likewise a false statement.
Yeah, I remembered there being a section on returning cursors. I went
to the docs page and seached, and found it here:
On Feb 19, 2008 9:38 PM, hewei [EMAIL PROTECTED] wrote:
Hi,Every body;
I have a table contains 100,000 rows, and has a primary key(int).
Now ,I need to execute sql command like update .. where id=*(id
is primary key).
I expect execute 1200-1600 sqlcommands per
On Feb 19, 2008 10:37 PM, serafin segador [EMAIL PROTECTED] wrote:
hello list,
i am a newbie in postgresql.
Why are you posting the same request twice?
i ported a small application to postgresql 8.2 originally written to store
data in maxdb. since stored procedures are not supported in
Hello
Have the same problem but in ordinary usage,no replication or
whatsoever. Problem is when client connects to the DB,stored procedure
in its initialization check mapping between some_table_name and
corresponding OID. Once something is changed in DB,for example OID's
deleted and
59 matches
Mail list logo
