"Francisco Figueiredo Jr." <[EMAIL PROTECTED]> writes:
> I'm implementing the 3.0 protocol version in Npgsql, a .Net Data
> provider for postgresql.
> I stopped in the first message: Parse :(
> I send the parse message but I don't receive the ParseComplete or the
> ErrorResponse. My code simply
Christopher Kings-Lynne <[EMAIL PROTECTED]> writes:
>>> Will I destroy things if I execute
>>> update pg_proc set probin = '/usr/lib/pgsql/plpgsql.so' where proname =
>>> 'plpgsql_call_handler';
>>
>> Nope ... that's what I'd probably do.
> Even better change it to '$libdir/plpgsql.so'.
Good po
Hi all,
I'm playing with this for one week with no luck... :(
I'm implementing the 3.0 protocol version in Npgsql, a .Net Data
provider for postgresql.
I could get it working using the simple query and so, I started to work
in the extended query.
I stopped in the first message: Parse :(
I
A long, long time.
Chris
On Thu, 26 Jun 2003, Shirish Reddy wrote:
> Hi,
>
> One of the issues that is preventing us from migrating
> from an Oracle DB to Postgres is that Table
> Partitioning is not available in Postgres yet.
> Partitioning is still listed as a TO DO. Any ideas
> when this will
> > Will I destroy things if I execute
> > update pg_proc set probin = '/usr/lib/pgsql/plpgsql.so' where proname =
> > 'plpgsql_call_handler';
>
> Nope ... that's what I'd probably do. You could alternatively use
> CREATE OR REPLACE FUNCTION if you wanted to be pure, but I'd say that
> that c
No, they're not.
Chris
On 27 Jun 2003, Austin Gonyou wrote:
> I thought Tablespaces were already implemented. Are they not?
>
>
> On Thu, 2003-06-26 at 22:10, Christopher Kings-Lynne wrote:
> > > ROTFL... the answer is no. Feature freeze is Tuesday, people. In
> > > practice, the time to start
Bruce Momjian <[EMAIL PROTECTED]> writes:
> I am seeing this assembler warning using gcc version 2.95.3 20010315:
> {standard input}:332: Warning: using `%si' instead of `%esi' due to `w' uffix
> {standard input}:332: Warning: using `%ax' instead of `%eax' due to `w' suffix
Bizarro. When did yo
Tom Lane wrote:
Joe Conway <[EMAIL PROTECTED]> writes:
So array[] should produce '{}' of (an array) type determined by the
context? OK -- seems easy enough.
Is it? I think we'd decided that this could only reasonably be handled
by creating a datatype representing array-of-UNKNOWN. I'm afraid to
Joe Conway <[EMAIL PROTECTED]> writes:
> So array[] should produce '{}' of (an array) type determined by the
> context? OK -- seems easy enough.
Is it? I think we'd decided that this could only reasonably be handled
by creating a datatype representing array-of-UNKNOWN. I'm afraid to do
that bec
Tom Lane wrote:
It's just a matter of staking out what's considered an implemented
feature. The ARRAY[] syntax is definitely in, so if it needs a few
adjustments around the edges to make it more spec-compliant, no one
will blink at doing that during beta.
OK, but some of what Peter requested were
On Thu, Jun 26, 2003 at 09:27:23 -0700,
Shirish Reddy <[EMAIL PROTECTED]> wrote:
> Hi,
>
> One of the issues that is preventing us from migrating
> from an Oracle DB to Postgres is that Table
> Partitioning is not available in Postgres yet.
> Partitioning is still listed as a TO DO. Any ideas
>
On Thu, Jun 26, 2003 at 07:32:02 -0700,
Ryan Mack <[EMAIL PROTECTED]> wrote:
> The query planner does an abysmal job with some of the most important
> views in my DB. The execuation time with seq_scan disabled is 25ms versus
> 110ms when seq_scan is enabled. Instead of modifying all my code to
Bruce Momjian <[EMAIL PROTECTED]> writes:
> Joe Conway wrote:
>> Yeah, but isn't feature freeze July 1?
> Yes, but once the "feature" is in, you can adjust it if it isn't
> working.
> I am just pointing out that beating the system is a popular hacker
> passtime during beta. :-)
It's just a matte
Hi, folks;
We're running Postgres 7.3.2.
At the end of some procedure we get a core dump on HP-11.
This does not seem reproducible on Solaris or Linux.
Working with debugger we get this stack:
#0 0xc0185a20 in mallinfo+0x2144 () from /usr/lib/libc.2
(gdb) where
#0 0xc0185a20 in mallinfo+0x2144 ()
Hi,
One of the issues that is preventing us from migrating
from an Oracle DB to Postgres is that Table
Partitioning is not available in Postgres yet.
Partitioning is still listed as a TO DO. Any ideas
when this will be available in Postgres? Approximate
time frame will be good enough for now.
Tha
The query planner does an abysmal job with some of the most important
views in my DB. The execuation time with seq_scan disabled is 25ms versus
110ms when seq_scan is enabled. Instead of modifying all my code to
temporarily disable seq_scan around all places this query is made (or
making a proced
Wow.
I just want to express my appreciation to Tom and the rest of the
folks in the PostgreSQL community. You can be sure that this little
episode, in which less than 48 hours passed from bug discovery to
patch, will make it into my future talks about the wonders of
open-source software.
I'm ext
En un mensaje anterior, [EMAIL PROTECTED] escribió:
> > Well, correct solution is to implement tablespaces on which objects like
> > databases, tables and indexes can be put.
>
> I've not looked at the SQL standard, but it seems to me like the order
> should be:
>
> Databases
>Tablespaces
On Wed, 2003-06-25 at 10:51, Jonathan Bartlett wrote:
> My solution did not involve tablespaces, but was more of a quick solution
> to make it easier for admins to do _some_ sort of physical configuration.
>
> The idea is that the developer could do something like
>
> 'create alternate location A
Adam Haberlach <[EMAIL PROTECTED]> writes:
> Will I destroy things if I execute
> update pg_proc set probin = '/usr/lib/pgsql/plpgsql.so' where proname =
> 'plpgsql_call_handler';
Nope ... that's what I'd probably do. You could alternatively use
CREATE OR REPLACE FUNCTION if you wanted to
Peter Eisentraut <[EMAIL PROTECTED]> writes:
> The documentation says the following is allowed:
> INSERT INTO sal_emp
> VALUES ('Bill',
> ARRAY[1, 1, 1, 1],
> ARRAY[['meeting', 'lunch'], ['','']]);
> I cannot find justification for this in the standard. According to my
I am seeing this assembler warning using gcc version 2.95.3 20010315:
{standard input}:332: Warning: using `%si' instead of `%esi' due to `w' uffix
{standard input}:332: Warning: using `%ax' instead of `%eax' due to `w' suffix
This is while compiling commands/trigger.c and it happens in
CreateT
No, they're not. There are some folks who have hacked on them in the
past, but nothing's been committed.
On 27 Jun 2003, Austin Gonyou wrote:
> I thought Tablespaces were already implemented. Are they not?
>
>
> On Thu, 2003-06-26 at 22:10, Christopher Kings-Lynne wrote:
> > > ROTFL... the an
> I thought Tablespaces were already implemented. Are they not?
Apparently not.
A group has been formed to work on it, though.
--
Mike Nolan
---(end of broadcast)---
TIP 7: don't forget to increase your free space map settings
Peter Eisentraut wrote:
The documentation says the following is allowed:
INSERT INTO sal_emp
VALUES ('Bill',
ARRAY[1, 1, 1, 1],
ARRAY[['meeting', 'lunch'], ['','']]);
I cannot find justification for this in the standard. According to my
reading, it should be
INSERT INT
I thought Tablespaces were already implemented. Are they not?
On Thu, 2003-06-26 at 22:10, Christopher Kings-Lynne wrote:
> > ROTFL... the answer is no. Feature freeze is Tuesday, people. In
> > practice, the time to start coding new stuff is already long past.
> > Especially major new stuff.
>
Joe Conway wrote:
> Bruce Momjian wrote:
> >>None of this is very difficult. I'll try to fit it in between now and
> >>Monday evening, but if not it's very doable for 7.5.
> >
> > Joe, you have to get in the swing of things --- beta isn't until July
> > 15, and even after that, you can fix bugs,
Bruce Momjian wrote:
None of this is very difficult. I'll try to fit it in between now and
Monday evening, but if not it's very doable for 7.5.
Joe, you have to get in the swing of things --- beta isn't until July
15, and even after that, you can fix bugs, so once it is in, you can
fiddle with it
> > * Some information schema work (doing that now...)
> >
> So I take it I need not worry about that?
>
>
> None of this is very difficult. I'll try to fit it in between now and
> Monday evening, but if not it's very doable for 7.5.
Joe, you have to get in the swing of things --- beta isn't u
Peter Eisentraut wrote:
Some nice advances to SQL standard array support were made, but there are
a few things that don't work yet in the sense of feature S091 "Basic array
support". Joe, do you want to take on some of these? They should be
pretty easy (for you).
* Declaration of multidimensional
Wow, I am impressed by 'gmake check'. Who did all that work? It is
great.
I modified tools/pgtest to use 'gmake check'. Thanks.
---
Peter Eisentraut wrote:
> Bruce Momjian writes:
>
> > Amazing you find 688 bytes worth
I know that we're all in end-of-release hurry, but I've got a quick
question.
We've got some machines that had postgres installed in /usr/local/pgsql
and we are moving their data directories, wholesale, onto machines with
postgres in the standard RedHat locations. This works just
Attached is a 7.2.4 dump (loads without error) and a 7.4 dump (loads
with error).
Create user "rbt" prior to loading either.
Creation of the database was done by:
rbttest=# create table tab (col integer);
CREATE
rbttest=# grant all on tab to public;
GRANT
On Fri, 2003-06-27 at 15:59, Peter Ei
Rod Taylor writes:
> psql:22.sql:2324: ERROR: dependent privileges exist (use CASCADE to
> revoke them too)
>
> Line 2324 is:
> REVOKE ALL ON TABLE sh2bill_action_action_id_seq FROM rbt;
>
> This user was the owner of of the sequence on the old database.
I'd need to see a complete and standalone
Alvaro Herrera Munoz writes:
> Is there a way to create a table from a prepared statement? CREATE TABLE AS
> explicitly says you have to use a SELECT statement, and the SELECT INTO
> syntax doesn't seem to allow the use of a prepared statement either. I
> don't see a way to use the prepared stat
The documentation says the following is allowed:
INSERT INTO sal_emp
VALUES ('Bill',
ARRAY[1, 1, 1, 1],
ARRAY[['meeting', 'lunch'], ['','']]);
I cannot find justification for this in the standard. According to my
reading, it should be
INSERT INTO sal_emp
VALUES (
Some nice advances to SQL standard array support were made, but there are
a few things that don't work yet in the sense of feature S091 "Basic array
support". Joe, do you want to take on some of these? They should be
pretty easy (for you).
* Declaration of multidimensional arrays (see clause 6.1
Using the 7.4 pg_dump to dump a 7.2 database, restoration to 7.4 causes:
REVOKE
GRANT
psql:22.sql:2324: ERROR: dependent privileges exist (use CASCADE to
revoke them too)
Line 2324 is:
REVOKE ALL ON TABLE sh2bill_action_action_id_seq FROM rbt;
This user was the owner of of the sequence on the o
On Fri, 2003-06-27 at 10:32, Tom Lane wrote:
> Aizaz, if you look at backend/main/main.c it should be pretty obvious
> how to handle this --- it's just like bootstrap mode. main.c kicks off
> control to GucInfoMain or whatever we call it, and then that routine
> can act pretty much the same as if
On Sun, 22 Jun 2003, Tom Lane wrote:
> Kevin Jacobs <[EMAIL PROTECTED]> writes:
> > Attached is a patch that removes all of the RExec code from plpython from
> > the current PostgreSQL CVS. In addition, plpython needs to be changed to an
> > untrusted language in createlang.
>
> I am inclined to
Hi.
I implement 2Q algorithm to PostgreSQL for buffer management , instead
of LRU.
It's known as low overhead and high performance than LRU. If you have
some interests , see following URL.
http://www.vldb.org/conf/1994/P439.PDF
In my test (pgbench -S) , it improves 4% cache hit rate and 2% up
pe
Tatsuo Ishii wrote:
>
> > Hello,
> > I reported bug #943 (I found in 7.3.2) and you checked in some change against
> > integer overflow.
> > Now I upgraded to 7.3.3 and I'm not happy with this.
> > The exact error as I described is fixed, but I found new errors in conversion
> > UTF-8 <-> EUC_TW
Hi Tom,
> I am inclined to rename plpython to plpythonu, by analogy to pltclu.
> The advantage of doing so is that (a) the name change makes it somewhat
> more obvious that there's a fundamental behavioral change, and (b)
> assuming that the Python folk someday figure out a secure version of
> REx
On Fri, 2003-06-27 at 03:21, James Pye wrote:
> Greets,
>
> Just a thought for a psql enhancement, afiak, it is not easily possible for
> persistent connections to a database in a shell script..
> The ability for psql to remain in the background reading from stdin and
> writing to st
Alvaro Herrera Munoz <[EMAIL PROTECTED]> writes:
> Is there a way to create a table from a prepared statement? CREATE TABLE AS
> explicitly says you have to use a SELECT statement, and the SELECT INTO
> syntax doesn't seem to allow the use of a prepared statement either.
IIRC there is an EXECUTE
Hackers,
Is there a way to create a table from a prepared statement? CREATE TABLE AS
explicitly says you have to use a SELECT statement, and the SELECT INTO
syntax doesn't seem to allow the use of a prepared statement either. I
don't see a way to use the prepared statement as a function nor as a
Aizaz Ahmed <[EMAIL PROTECTED]> writes:
> On Fri, 2003-06-27 at 11:52, Josh Berkus wrote:
>> Are you suggesting putting a copy of the list of GUCs in a system table? I'd
>> be for that
> hmmm ... I thought what this meant was that we don't factor the tables
> out into guc_vars.h, but leave
On Fri, 2003-06-27 at 11:52, Josh Berkus wrote:
> Are you suggesting putting a copy of the list of GUCs in a system table? I'd
> be for that
hmmm ... I thought what this meant was that we don't factor the tables
out into guc_vars.h, but leave them in guc.c. (adding the descriptions
etc. th
Josh Berkus <[EMAIL PROTECTED]> writes:
> Are you suggesting putting a copy of the list of GUCs in a system
> table?
Aizaz is not doing that, but see Joe Conway's proposed patch to
pg_settings.
regards, tom lane
---(end of broadcast)---
Tom,
> Aizaz, if you look at backend/main/main.c it should be pretty obvious
> how to handle this --- it's just like bootstrap mode. main.c kicks off
> control to GucInfoMain or whatever we call it, and then that routine
> can act pretty much the same as if it were the actual main() of a
> standa
Peter Eisentraut wrote:
>Thomas Swan writes:
>
>
>
>>I just am really concerned about the uninstall/clean up phase and how
>>that can be done in an orderly fashion. Unless the process can start
>>from a clean state again, then it won't be valid.
>>
>>
>
>The only clean state is if you remov
Srikanth,
> See the developers FAQ on how to get involved. You can send the patch
> to the patches list, of course.
http://developer.postgresql.org/readtext.php?src/FAQ/FAQ_DEV.html+Developers-FAQ
--
Josh Berkus
Aglio Database Solutions
San Francisco
---(end of broadca
Peter Eisentraut <[EMAIL PROTECTED]> writes:
> Joe Conway writes:
>> I was thinking something similar. This exact question has come up at
>> least three times in the last three months. I doubt we'd want a special
>> keyword like CURRENT_QUERY, but maybe current_query()?
> The current statement can
Bruce Momjian writes:
> Amazing you find 688 bytes worth discussing. I know you said "what
> happens if everyone adds their scripts", but something that would be a
> mess if everyone did it isn't always a proper way to judge if something
> is appropriate.
I said, if everyone adds their test meth
Srikanth M wrote:
>
> Hi
>
> We have written code for a DATACUBE in PostgreSQL. We would like
> to know how and what to submit , and if there is some specific procedure
> to submit our work. Please tell us the e-mail ID we have to send the
> information to also.
See the developers FAQ o
Peter Eisentraut <[EMAIL PROTECTED]> writes:
> Fernando Nasser writes:
>> We have a server side GUI utility that among other things let us configure GUC
>> variables. We badly need to know what variables exist in the specific backend
>> version, which are the min and max values and if possible a d
Manfred Koizar writes:
> I do this all the time. Works pretty well. The only minor annoyance
> is that some files are created in the source tree:
This is intentional, because said files are prebuilt in the distribution,
so they always have to be in the source directory.
--
Peter Eisentraut
Thomas Swan writes:
> I just am really concerned about the uninstall/clean up phase and how
> that can be done in an orderly fashion. Unless the process can start
> from a clean state again, then it won't be valid.
The only clean state is if you remove the entire source tree and check it
out aga
Tom Lane writes:
> This is something that breaks regularly because few of the key
> developers use it :-(. If there were automatic tests that used that
> build setup, it would be a good thing 'cause it'd keep us honest.
This should be included in 'make distcheck'. I'm quite puzzled right now
wh
Manfred Koizar <[EMAIL PROTECTED]> writes:
> I do this all the time. Works pretty well. The only minor annoyance
> is that some files are created in the source tree:
Yeah, that's deliberate: those files are shipped in distribution
tarballs (so that tarball users don't have to have bison/flex/per
Hi
We have written code for a DATACUBE in PostgreSQL. We would like
to know how and what to submit , and if there is some specific procedure
to submit our work. Please tell us the e-mail ID we have to send the
information to also.
---(end of broadcast)
On Fri, 2003-06-27 at 08:36, Peter Eisentraut wrote:
> The system catalog columns pg_attrdef.adsrc and pg_constraint.consrc store
> "human-readable" versions of pg_attrdef.adbin and pg_constraint.conbin.
> During a rename operation, they are not and cannot be updated. We need to
> remove them and
On Friday, June 27, 2003, at 02:00 AM, Tom Lane wrote:
We've only had domains for one release cycle, so it seems to me that
there's not a lot of track record to justify a "this is how we've
always
done it" position for domain-related behaviors. Especially when the
odds seem good that few people
Fernando Nasser writes:
> We have a server side GUI utility that among other things let us configure GUC
> variables. We badly need to know what variables exist in the specific backend
> version, which are the min and max values and if possible a description.
In that case I think it's best to pu
John DeSoi writes:
> To me this seems completely wrong. The whole point of getting the
> domain is so that I can know how I should parse the result coming from
> the server. If I use a text domain, I can't distinguish the domain
> column from any other text column and perform some other kind of
>
Joe Conway writes:
> I was thinking something similar. This exact question has come up at
> least three times in the last three months. I doubt we'd want a special
> keyword like CURRENT_QUERY, but maybe current_query()?
The current statement can be examined using the statistics views and
functio
The system catalog columns pg_attrdef.adsrc and pg_constraint.consrc store
"human-readable" versions of pg_attrdef.adbin and pg_constraint.conbin.
During a rename operation, they are not and cannot be updated. We need to
remove them and make interested applications get the information about of
the
On Thu, 26 Jun 2003 22:55:45 -0400, Tom Lane <[EMAIL PROTECTED]>
wrote:
>> I've not tried, but if PostgreSQL can do an 'out of tree' compile it
>> could make it much easier.
>
>Yes it can, following the usual procedure for autoconfiscated trees:
>just invoke configure from an empty directory, eg
>
Greets,
Just a thought for a psql enhancement, afiak, it is not easily possible for
persistent connections to a database in a shell script..
The ability for psql to remain in the background reading from stdin and
writing to stdout until explicitly killed. More specifically, so a
69 matches
Mail list logo
