> > This sounds like a known bug in 8.2.x --- it's fixed for 8.2.4. If
> > you can still reproduce it with 8.2.4, please provide the test case.
>
> Hi Tom, thanks for the response.
>
> I must have missed it, but when was 8.2.4 released? I don't recall any
> announcement, and the website still s
On Sun, Apr 22, 2007 at 06:52:33PM -0400, Brad Buran wrote:
> I'm trying to learn how to write custom extensions to postgres so wrote a
> basic C function to see how it works. However, I keep getting the following
> error "Missing magic block" when I try to add the function to the database.
> Acco
On Mon, Apr 23, 2007 at 12:31:32AM -0400, Tom Lane wrote:
> [EMAIL PROTECTED] writes:
> > When I try to initiate tsearch2 in 8.2.4, I got the following error.
> > ERROR: incompatible library "/usr/local/pgsql/lib/tsearch2.so":
> > missing magic block
>
> Apparently you have a pre-8.2 version inst
On Sun, 22 Apr 2007, Roland Turner wrote:
> I'm working with 7.4, but the 8.2 docs[1] have the same apparent error:
>
> ROW SHARE
>
> Conflicts with the EXCLUSIVE and ACCESS EXCLUSIVE lock modes.
>
> The SELECT FOR UPDATE and SELECT FOR SHARE commands acquire a
> lock of th
am Mon, dem 23.04.2007, um 10:51:31 +0530 mailte Mageshwaran folgendes:
> Hi ,
>
> I am new to postgresql, I have been assigned a task of upgrading
> postgresql to higher version.
> In our company we are using 7.1.1,7.1.3,7.4.5 versions of postgresql,
> can you please tell me which is the stable
Hi ,
I am new to postgresql, I have been assigned a task of upgrading
postgresql to higher version.
In our company we are using 7.1.1,7.1.3,7.4.5 versions of postgresql,
can you please tell me which is the stable and suitable version in 8.x
version.
Please reply me,
Regards
J Mageshwaran
*
Roland Turner <[EMAIL PROTECTED]> writes:
> I'm working with 7.4, but the 8.2 docs[1] have the same apparent error:
> ROW SHARE
> Conflicts with the EXCLUSIVE and ACCESS EXCLUSIVE lock modes.
> If that conflict list were correct, then ROW SHARE wouldn't conflict
> with itself, mu
[EMAIL PROTECTED] writes:
> When I try to initiate tsearch2 in 8.2.4, I got the following error.
> ERROR: incompatible library "/usr/local/pgsql/lib/tsearch2.so":
> missing magic block
Apparently you have a pre-8.2 version installed in /usr/local.
Update.
regards, tom lan
I'm trying to learn how to write custom extensions to postgres so wrote a
basic C function to see how it works. However, I keep getting the following
error "Missing magic block" when I try to add the function to the database.
According to the documentation in the manual, all I need to do is add th
I've had some difficulty with pgFoundry and can't find out how to e-mail the
administrator (I assume there is one). In my Komo project, it appears the open
mailing list is getting some spam (komo-client-commits) and I wanted to remove
this. Second, I've received a request for reply on this lis
On Apr 20, 11:38 pm, [EMAIL PROTECTED] wrote:
> When I try to initiate tsearch2 in 8.2.4, I got the following error.
>
> $ psql emedia_db < tsearch2.sql
> SET
> BEGIN
> NOTICE: CREATE TABLE / PRIMARY KEY will create implicit index
> "pg_ts_dict_pkey" for table "pg_ts_dict"
> CREATE TABLE
> ERROR:
I want to allow "notes" on any row in any table in my database. A
table row may have multiple notes. Say my tables are "foo," "bar," and
"qux." I want to avoid having a lookup table for each of them
("foo_notes," "bar_notes," and "qux_notes").
Is there a standard way of solving this problem?
Not
In article <[EMAIL PROTECTED]>,
<[EMAIL PROTECTED]> wrote:
% On Apr 20, 11:38 pm, [EMAIL PROTECTED] wrote:
% > When I try to initiate tsearch2 in 8.2.4, I got the following error.
% >
% > $ psql emedia_db < tsearch2.sql
% > SET
% > BEGIN
% > NOTICE: CREATE TABLE / PRIMARY KEY will create implicit
I'm working with 7.4, but the 8.2 docs[1] have the same apparent error:
ROW SHARE
Conflicts with the EXCLUSIVE and ACCESS EXCLUSIVE lock modes.
The SELECT FOR UPDATE and SELECT FOR SHARE commands acquire a
lock of this mode on the target table(s) (in addi
When I try to initiate tsearch2 in 8.2.4, I got the following error.
$ psql emedia_db < tsearch2.sql
SET
BEGIN
NOTICE: CREATE TABLE / PRIMARY KEY will create implicit index
"pg_ts_dict_pkey" for table "pg_ts_dict"
CREATE TABLE
ERROR: incompatible library "/usr/local/pgsql/lib/tsearch2.so":
missi
"carter ck" <[EMAIL PROTECTED]> writes:
> I am wonderring the differences between creating an index on several columns
> of a table and an index on each column of a table.
> For example, following is my select query:
> select * from my_table where myrowid='abc' and mytask='TEst 1' and
> myday!=
Hi all,
I am wonderring the differences between creating an index on several columns
of a table and an index on each column of a table.
For example, following is my select query:
select * from my_table where myrowid='abc' and mytask='TEst 1' and
myday!='holiday';
Which of the following is
> We require that all submissions conform to the Postgres BSD license,
> but we are not picky about requiring paperwork to prove it. Just put
> the same copyright header into any added files as you see in existing
> files.
OK cool.
> Yeah, the core team does not have a lot of bandwidth right now
On 21/04/2007 23:41, Tom Lane wrote:
This sounds like a known bug in 8.2.x --- it's fixed for 8.2.4. If
you can still reproduce it with 8.2.4, please provide the test case.
Hi Tom, thanks for the response.
I must have missed it, but when was 8.2.4 released? I don't recall any
announcement,
"Robert Haas" <[EMAIL PROTECTED]> writes:
> 1. Does the PostgreSQL development team require the assignment of
> copyright in order to accept contributions? If so, is there a standard
> form that is normally used for this purpose? Or, alternatively, do I
> need to provide something that says that
chrisj wrote:
Thanks Brent, very much appreciated, your first suggestion is perfect.
the translate suggestion assumes that there are no commas in the data, but
that is why I wanted to use tab.
I figured as much :-) Note that you can use -F "|" for a pipe symbol, or
use any other character as
These may be more -hackers questions, but I am duly following protocol
by trying elsewhere first.
1. Does the PostgreSQL development team require the assignment of
copyright in order to accept contributions? If so, is there a standard
form that is normally used for this purpose? Or, alternativel
Or use a SAVEPOINT. I don't know about the impact on resources if you
leave it hanging around for a long time, but I use these for exactly
the scenario you are talking about.
- Ian
On 4/16/07, Martin Langhoff <[EMAIL PROTECTED]> wrote:
On 4/17/07, Tom Lane <[EMAIL PROTECTED]> wrote:
> Seems ov
"Seq Scan on" - is this just a FULL TABLE scan?
I'm familiar with Oracles explain plans and terminology.
But not so much so with psql...
---(end of broadcast)---
TIP 4: Have you searched our list archives?
http://archives.postgresql
am Sun, dem 22.04.2007, um 9:43:32 -0400 mailte Tom Allison folgendes:
> "Seq Scan on" - is this just a FULL TABLE scan?
Yes.
Andreas
--
Andreas Kretschmer
Kontakt: Heynitz: 035242/47150, D1: 0160/7141639 (mehr: -> Header)
GnuPG-ID: 0x3FFF606C, privat 0x7F4584DA http://wwwkeys.de.pgp.
25 matches
Mail list logo
