Hi, all
I have installed the Postgresql 7.3 . But I think something is wrong with
authority.
I have made the following operations:
1. I enter the psql and run 'alter user postgres with password
'postgres''
2. I change the pg_hba.conf and set the auth_type from 'trust' to
'password
Hi all
I have install Postgresql 7.3 with user name EDU.then I enter the psql to
change the password for EDU using "alter user EDU with password '''it
returns " user EDU do not exist".I check the system table pg_user, and the
user 'EDU' actually exists.But if I tak
Hi all,
I will to make the SQL 92/99 conformance test for Postgresql, could you give
me some advices
on which tool can meet the demand ?
Great thanks for any message.
Josh
Hello to any person who is interested:
Our team are trying hard on the PostgreSQL test,including JDBC,ODBC,SQL.
Could anyone give us some instructions about SQL Conformance?
We've got NIST's SQL Test Suite V6 and tried it.But after checking its some SQL
scripts,I found
it was not as good
Hello to any person who is interested:
Our team are trying hard on the PostgreSQL test,including JDBC,ODBC,SQL.
Could anyone give us some instructions about SQL Conformance?
We've got NIST's SQL Test Suite V6 and tried it.But after checking its some SQL
scripts,I found
it was not as good
Hi all.
I have read some codes on transaction abort
operation. When the transaction abort, it seem that
all the tuples related in the transaction have not been deal with. it XMIN
equals to the tuple create transaction
ID. ItsXMAX equals null. Of cource ,It make some records on
the
Hi allI have read some code on transaction part.When the new
transaction starts, it record the snapshot of database containing the current
transaction id,etc. So depending on the snapshot, the transaction decide
which tuple is visible.But transaction could also be implemented by lock. so
Hannu Krosing wrote:
Have you found out _what_ exaclty is patented ?
Is it just his concrete implementation of UB-Tree or something
broader, like using one multi-dimensional index instead of multiple
one-dimensional ones ?
(I know it is OT, please reply in private, I can summarize any
Hi all
I have read some code on transaction part.
When the new transaction starts, it record the snapshot of database containing the
current transaction id,etc. So depending on the snapshot
, the transaction decide which tuple is visible.
But transaction could also be implemented by lock. so I am
Hi all.
I am newer to postgresql develop, so my qestion maybe too simple.
I have noticed that we have discussed the incremental backup and PITR before.
Frankly, I am still interested in incremental backup. I am not sure
whether we can implement such function based on XLog
Since there exists
Hi all
Can anyone tell me the approximate pg 7.5 release date?
Thanks
Josh
---(end of broadcast)---
TIP 4: Don't 'kill -9' the postmaster
postgresql source code is at c:/mingw/postgresql and instal to
C:/msys/1.0/local/pgsql/
I add a function to src\backend\utils\adt\geo_ops.c as the following:
/Datum
box_add2(PG_FUNCTION_ARGS)
{
BOX *box = PG_GETARG_BOX_P(0);
Point*p = PG_GETARG_POINT_P(1
* [PATCHES] Updateable cursors patch /FAST PostgreSQL/
This is incomplete, and I fear at this point has to be held over to 8.4.
It is true that my original patch post said that I need to modify the
patch to work with tidscan. Since then I have realized that this
modification is not needed
Andrew Dunstan wrote:
The CSVlog pipe is a separate pipe from the stderr pipe. Anything that
goes to stderr now will continue to go to stderr, wherever that is.
I like this scheme for a couple of reasons:
. it will include the ability to tell the real end of a message
. it will let us
Andrew Dunstan wrote:
Now that we've fixed the partial/interleaved log line issue, I have
returned to trying toi get the CSV log patch into shape. Sadly, it still
needs lots of work, even after Greg Smith and I both attacked it, so I
am now going through it with a fine tooth comb.
One
In CVS HEAD
workspace=# begin;
BEGIN
workspace=# declare cu cursor for select * from t1 for read only;
DECLARE CURSOR
workspace=# fetch cu;
a
---
1
(1 row)
workspace=# delete from t1 where current of cu;
DELETE 1
workspace=# commit;
COMMIT
Is this the intended behaviour? If so should we
Josh Berkus wrote:
Arul Shaji
Sydney, Australia.
Rgds,
Arul Shaji
Hi All,
I am now trying to implement pg_get_domaindef() function which is in the TODO
list and ran into a minor issue.
When the following command is given
CREATE DOMAIN testdomain AS text CONSTRAINT testconstraint NOT NULL;
I couldn't find the CONSTRAINT name ('testconstraint' in this case)
We are trying to develop the updateable cursors functionality into
Postgresql. I have given below details of the design and also issues we are
facing. Looking forward to the advice on how to proceed with these issues.
Rgds,
Arul Shaji
1. Introduction
--
This is a combined
On Tue, 23 Jan 2007 15:48, Joshua D. Drake wrote:
FAST PostgreSQL wrote:
We are trying to develop the updateable cursors functionality into
Postgresql. I have given below details of the design and also issues we
are facing. Looking forward to the advice on how to proceed
On Wed, 28 Feb 2007 09:48, Bruce Momjian wrote:
[Added a subejct line]
FYI, I am not going to be comfortable accepting a final patch that
contains this email signature:
This is an email from Fujitsu Australia Software Technology Pty Ltd, ABN
27 003 693 481. It is confidential to
On Thu, 1 Mar 2007 04:28, Bruce Momjian wrote:
I have added this to the developer's FAQ to clarify the situtation of
posting a patch:
liPostgreSQL is licensed under a BSD license. By posting a patch
to the public PostgreSQL mailling lists, you are giving the PostgreSQL
Global
On Fri, 2 Mar 2007 01:20, Simon Riggs wrote:
On Thu, 2007-03-01 at 15:17 +1100, FAST PostgreSQL wrote:
Hi Simon,
We are happy to provide that. If and when it comes to the final patch
being accepted, we can send a copyright waiver mail which will put our
source code contribution under
hello everybody,
we are seriously fighting with some planner issue which seems to be
slightly obscure to us.
we have a table which is nicely indexed (several GB in size).
i am using btree_gist operator classes to use a combined index including
an FTI expression along with a number:
db=# \d
Tom Lane wrote:
Hans-Juergen Schoenig -- PostgreSQL postg...@cybertec.at writes:
what we basically expected here is that Postgres will scan the table
using the index to give us the cheapest products containing the words we
are looking for.
i am totally surprised to see that we have to fetch
Andrew Dunstan wrote:
Werner Echezuria wrote:
Hi, I have a code in which I translate some code from sqlf to sql, but
when it comes to yy_parse the server crashes, I have no idea why,
because it works fine in other situations.
I don't understand why you're doing what you're doing this
to consider doing with partly with gist
and partly with a btree.
is there any option to adapt gist in a way that a combined index would
make sense here?
many thanks,
hans
Heikki Linnakangas wrote:
Hans-Juergen Schoenig -- PostgreSQL wrote:
my knowledge of how gist works
Tom,
On behalf of the entire PostgreSQL team here in Austria I want to wish
you a happy birthday.
We hope that you fill be a vital part of PostgreSQL for many years to come.
Best regards,
Hans-Jürgen Schönig + team
--
Cybertec Schoenig Schoenig GmbH
Reyergasse 9 / 2
A-2700 Wiener
.
btw, this old terminal application i was talking about is exactly the
usecase we had - this is why this patch has been made.
we are porting roughly 2500 terminal application from informix to
postgresql. we are talking about entire factory production lines and so
on here (the ECPG patches posted
Jeff Janes wrote:
Will statement_timeout not suffice for that use case?
we tried to get around it without actually touching the core but we
really need this functionality.
patching the core here is not the primary desire we have. it is all
about modeling some functionality which was truly
thanks,
hans
Oleg Bartunov wrote:
Hi there,
this is an announcement of our new contribution module for PostgreSQL
- Plantuner - enable planner hints
(http://www.sai.msu.su/~megera/wiki/plantuner).
Example:
=# LOAD 'plantuner';
=# create table test(id int);
=# create index id_idx on test
to do it the
best way. comments are welcome ...
note, this is a first draft i want to refine based on some comments.
here we go ...
Partial WAL Replication for PostgreSQL:
---
As of now the PostgreSQL community has provided patches and functionalities
which
*snip*
One pretty major fly in the ointment is that neither Hot Standby nor
Streaming Replication has been committed or shows much sign of being
about to be committed. I think this is bad. These are big features
that figure to have some bugs and break some things. If they're not
committed in
On Jun 24, 2010, at 2:13 PM, Michael Meskes wrote:
I think, yes, it does make sense. Because we are talking
about porting a whole lot of COBOL applications.
COBOL???
yes, COBOL :).
it is much more common than people think.
it is not the first COBOL request for PostgreSQL hitting my desk
hello everybody,
we are currently facing some serious issues with cross correlation issue.
consider: 10% of all people have breast cancer. we have 2 genders (50:50).
if i select all the men with breast cancer, i will get basically nobody - the
planner will overestimate the output.
this is the
On Jul 14, 2010, at 12:40 PM, Heikki Linnakangas wrote:
On 14/07/10 13:12, PostgreSQL - Hans-Jürgen Schönig wrote:
hello everybody,
we are currently facing some serious issues with cross correlation issue.
consider: 10% of all people have breast cancer. we have 2 genders (50:50).
if i
.
many thanks,
hans
On Jul 14, 2010, at 4:01 PM, Tom Lane wrote:
Heikki Linnakangas heikki.linnakan...@enterprisedb.com writes:
On 14/07/10 13:12, PostgreSQL - Hans-Jürgen Schönig wrote:
maybe somehow like this ...
ALTER TABLE x SET CORRELATION STATISTICS FOR (id = id2
hello ...
look at the syntax i posted in more detail:
ALTER TABLE x SET CORRELATION STATISTICS FOR (x.id = y.id AND x.id2 =
y.id2)
it says X and Y ...
the selectivity of joins are what i am most interested in. cross correlation of
columns within the same table are just a byproduct.
On Jul 25, 2010, at 11:56 AM, Martijn van Oosterhout wrote:
On Fri, Jul 23, 2010 at 10:04:00PM +0200, Hans-Jürgen Schönig wrote:
create table foo ( x date );
create table foo_2010 () INHERITS (foo)
create table foo_2009 () INHERITS (foo)
create table foo_2008 () INHERITS
able to sort a smaller result set.
--
Álvaro Herrera alvhe...@commandprompt.com
The PostgreSQL Company - Command Prompt, Inc.
PostgreSQL Replication, Consulting, Custom Development, 24x7 support
--
Cybertec Schönig Schönig GmbH
Gröhrmühlgasse 26
A-2700 Wiener Neustadt, Austria
Web: http
there.
unfortunately this code is not too well known.
many thanks,
hans
On Aug 30, 2010, at 9:41 PM, Pavel Stehule wrote:
2010/8/30 Pei He hepeim...@gmail.com:
Hi,
I am hacking postgresql 8.2.5. a) and b) do not work for me.
The situation is that I made a join operator
On Sep 1, 2010, at 4:10 PM, Tom Lane wrote:
Boszormenyi Zoltan z...@cybertec.at writes:
we are experimenting with modifying table partitioning
so the ORDER BY clause can be pushed down to
child nodes on the grounds that:
This is really premature, and anything you do along those lines now
hello tom,
yeah, we have followed quite a lot of discussion as well ...
and yes, no patches.
as far as this problem is concerned: we are working on a patch and did some
prototyping inside the planner already (attached).
the code we have is pretty limited atm (such as checking for a sort clause
hello everybody,
we came across an issue which turned out to be more serious than previously
expected.
imagine a system with, say, 1000 partitions (heavily indexed) or so. the time
taken by the planner is already fairly heavy in this case.
i tried this one with 5000 unindexed tables (just one
On Sep 3, 2010, at 2:04 PM, Stephen Frost wrote:
* PostgreSQL - Hans-Jürgen Schönig (postg...@cybertec.at) wrote:
did anybody think of a solution to this problem.
or more precisely: can there be a solution to this problem?
Please post to the correct list (-performance) and provide
On Sep 3, 2010, at 4:40 PM, Tom Lane wrote:
=?iso-8859-1?Q?PostgreSQL_-_Hans-J=FCrgen_Sch=F6nig?= postg...@cybertec.at
writes:
imagine a system with, say, 1000 partitions (heavily indexed) or so. the
time taken by the planner is already fairly heavy in this case.
As the fine manual
postgresql-8.4.0.old/contrib/Makefile postgresql-8.4.0/contrib/Makefile
*** postgresql-8.4.0.old/contrib/Makefile 2009-03-26 00:20:01.0 +0100
--- postgresql-8.4.0/contrib/Makefile 2009-06-29 11:03:04.0 +0200
*** WANTED_DIRS = \
*** 39,44
--- 39,45
tablefunc
hello,
this patch has not made it through yesterday, so i am trying to send it
again.
i made a small patch which i found useful for my personal tasks.
it would be nice to see this in 8.5. if not core then maybe contrib.
it transforms a tsvector to table format which is really nice for text
Hans-Juergen Schoenig -- PostgreSQL wrote:
hello,
this patch has not made it through yesterday, so i am trying to send
it again.
i made a small patch which i found useful for my personal tasks.
it would be nice to see this in 8.5. if not core then maybe contrib.
it transforms a tsvector
I have toyed around with KNN a little and I am pretty impressed when it comes
to the results we have seen in the GIS world.
Given the infrastructure we have at the moment I wonder if KNN can help to
speedup queries like that:
SELECT ... WHERE fti_query ORDER BY numeric_col LIMIT x
The use case
On May 22, 2012, at 9:57 AM, Simon Riggs wrote:
On 22 May 2012 06:50, Tom Lane t...@sss.pgh.pa.us wrote:
Currently, the planner keeps paths that appear to win on the grounds of
either cheapest startup cost or cheapest total cost. It suddenly struck
me that in many simple cases (viz, those
On Jun 16, 2012, at 8:27 AM, Magnus Hagander wrote:
I'm not sure if this is something I don't know how to do, or if it's
something we simply can't do, or if it's something we could do but the
syntax can't handle :-)
Basically, I'd like to combine a recursive and a non-recursive CTE in
the
hello ...
2.4? we know that some versions of 2.4 cause problems due to broken
posix_fadvise. if i remember correctly we built some configure magic into
PostgreSQL to check for this bug. what does this check do?
many thanks,
hans
On Jun 15, 2011, at 6:12 PM, Merlin
On Jun 23, 2011, at 12:52 AM, Alvaro Herrera wrote:
Excerpts from Joshua D. Drake's message of mié jun 22 15:37:17 -0400 2011:
Per:
http://archives.postgresql.org/pgsql-hackers/2010-11/msg02043.php
It seems we did come up with a use case in the procpid discussion. The
ability to change
On Jun 23, 2011, at 12:52 AM, Alvaro Herrera wrote:
Excerpts from Joshua D. Drake's message of mié jun 22 15:37:17 -0400 2011:
Per:
http://archives.postgresql.org/pgsql-hackers/2010-11/msg02043.php
It seems we did come up with a use case in the procpid discussion. The
ability to change
On Aug 7, 2011, at 11:01 AM, Simon Riggs wrote:
On Sun, Aug 7, 2011 at 8:57 AM, Hannu Krosing ha...@2ndquadrant.com wrote:
In 9.0 (as in earlier versions) a former standby host has to do a full
checkpoint before becoming available as an independent database instance
in either switchover or
On Aug 12, 2011, at 10:03 PM, Heikki Linnakangas wrote:
On 11.08.2011 23:06, Robert Haas wrote:
Comments, testing, review appreciated...
I would've expected this to use an index-only scan:
postgres=# CREATE TABLE foo AS SELECT generate_series(1,10) AS id;
SELECT 10
postgres=#
://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training Services
i would definitely argue for a syntax like the one proposed by Joachim.. i
could stay the same if this is turned into some sort of flashback
implementation some day.
regards,
hans
hello …
i have just fallen over a nasty problem (maybe missing feature) with PL/Pythonu
…
consider:
-- add a document to the corpus
CREATE OR REPLACE FUNCTION textprocess.add_to_corpus(lang text, t text) RETURNS
float4 AS $$
from SecondCorpus import SecondCorpus
from
On Aug 17, 2011, at 2:19 PM, Jan Urbański wrote:
On 17/08/11 14:09, PostgreSQL - Hans-Jürgen Schönig wrote:
CREATE OR REPLACE FUNCTION textprocess.add_to_corpus(lang text, t text)
RETURNS float4 AS $$
from SecondCorpus import SecondCorpus
from SecondDocument import
PostgreSQL Unlimited Scalability and Performance Consultant
2ndQuadrant Nordic
PG Admin Book: http://www.2ndQuadrant.com/books/
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
- and: this what would be
under your full control.
what do you think?
i got to think about it futher but i can envision that this could be feasible
...
hans
On Sep 2, 2011, at 2:36 PM, Hannu Krosing wrote:
On Fri, 2011-09-02 at 14:01 +0200, PostgreSQL - Hans-Jürgen Schönig
wrote:
hello …
i
On Sep 2, 2011, at 2:59 PM, Hannu Krosing wrote:
On Fri, 2011-09-02 at 14:51 +0200, PostgreSQL - Hans-Jürgen Schönig
wrote:
hello …
the goal of the entire proxy thing is to make the right query go to the
right node / nodes.
we determine this by using a partitioning function and so
look at two similar GPU codes which seem to do the same thing you
might easily see that one is 10 times faster than the other - for bloody reason
such as memory alignment, memory transaction size or whatever.
this opens a bit of a problem: PostgreSQL sorting is so generic and so flexible
that i
PostgreSQL failures on
HP-UX on a lame PA-RISC box. Looking at the PostgreSQL source code
then, I got an impression that running PostgreSQL on HP-UX was an open
question -- HP-UX didn't seem like a seriously targeted platform.
Was I wrong in my assessment? Does anybody have a good experience
On Oct 7, 2011, at 8:47 PM, Joshua D. Drake wrote:
On 10/07/2011 11:40 AM, Tom Lane wrote:
Robert Haasrobertmh...@gmail.com writes:
Please find attached a patch implementing a basic version of
index-only scans.
I'm making some progress with this, but I notice what seems like a
missing
hello everbody,
we have spent some time in finally attacking cross column correlation. as this
is an issue which keeps bugging us for a couple of applications (some years).
this is a WIP patch which can do:
special cross column correlation specific syntax:
On Feb 23, 2011, at 2:58 AM, Robert Haas wrote:
2011/2/22 PostgreSQL - Hans-Jürgen Schönig postg...@cybertec.at:
how does it work? we try to find suitable statistics for an arbitrary length
list of conditions so that the planner can use it directly rather than
multiplying all
Those are real problems, but I still want it. The last time I hit
this problem I spent two days redesigning my schema and adding
triggers all over the place to make things work. If I had been
dealing with a 30TB database instead of a 300MB database I would have
been royally up a creek.
by this).
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
i think the main issue is: what we do is ugly because of despair and a lack of
alternative ... what you proposed is ugly by design ;).
overall: the workaround will win the ugliness contest
On Feb 23, 2011, at 3:46 PM, Robert Haas wrote:
On Wed, Feb 23, 2011 at 12:50 AM, Nathan Boley npbo...@gmail.com wrote:
Personally, I think the first thing we ought to do is add a real, bona
fide planner hint to override the selectivity calculation manually,
maybe something like this:
On Feb 24, 2011, at 2:09 AM, Josh Berkus wrote:
Personally, I think the first thing we ought to do is add a real, bona
fide planner hint to override the selectivity calculation manually,
maybe something like this:
WHERE (x 5 AND y = 1) SELECTIVITY (0.1);
Then, having provided a method
types of machines, each with different customer data that
vary so much that queries need to be rather generic.
Postgresql shows its strength with planner doing a good job for different
variants of data, however we do a very little tweaking to the configuration
parameters. Just because it is just
hello ...
i have put some research into that some time ago and as far as i have seen
there is a 99% chance that no other database can do it the way we do it. it
seems nobody comes even close to it (especially not in the flexibility-arena).
oracle: disgusting workaround ...
hello all ...
given oleg's posting before i also wanted to fire up some KNN related question.
let us consider a simple example. i got some million lines and i want all rows
matching a tsquery sorted by price.
i did some tests:
test=# explain (analyze true, buffers true, costs true) SELECT id
) @@ '''mar'''::tsquery))
(3 rows)
On Fri, 8 Apr 2011, PostgreSQL - Hans-J?rgen Sch?nig wrote:
hello all ...
given oleg's posting before i also wanted to fire up some KNN related
question.
let us consider a simple example. i got some million lines and i want all
rows matching a tsquery
,
hans
On Apr 8, 2011, at 5:25 PM, Oleg Bartunov wrote:
Hans,
what if you create index (price,title) ?
On Fri, 8 Apr 2011, PostgreSQL - Hans-J?rgen Sch?nig wrote:
hello ...
i got that one ...
idx_product_t_product_titleprice gist (to_tsvector('german'::regconfig,
title
had a case where a client asked if PostgreSQL is locked during
base backup. of
course it was just disk wait caused by a full speed pg_basebackup.
regarding the client side implementation: we have chosen this way because it is
less invasive.
i cannot see a reason to do this on the server side
On Aug 21, 2013, at 10:57 AM, Andres Freund wrote:
On 2013-08-21 08:10:42 +0200, PostgreSQL - Hans-Jürgen Schönig wrote:
On Aug 19, 2013, at 9:11 PM, Andres Freund wrote:
On 2013-08-19 20:15:51 +0200, Boszormenyi Zoltan wrote:
2013-08-19 19:20 keltezéssel, Andres Freund írta:
Hi
i think there is one more thing which would be really good in GIN and which
would solve a ton of issues.
atm GIN entries are sorted by item pointer.
if we could sort them by a column it would fix a couple of real work issues
such as ...
SELECT ... FROM foo WHERE tsearch_query ORDER BY
On 18 Aug 2015, at 11:19, Albe Laurenz laurenz.a...@wien.gv.at wrote:
Hans-Jürgen Schönig wrote:
in addition to that you have the “problem” of transactions. if you failover
in the middle
of a transaction, strange things might happen from the application point of
view.
the good thing,
On 18 Aug 2015, at 10:32, Albe Laurenz laurenz.a...@wien.gv.at wrote:
Victor Wagner wrote:
Rationale
=
Since introduction of the WAL-based replication into the PostgreSQL, it is
possible to create high-availability and load-balancing clusters.
However, there is no support
gh.
(It's not really clear to me what this buys us over an encrypted FS,
other than a feature comparison checkmark...)
the reason why this is needed is actually very simple: security
guidelines and legal requirements ...
we have dealt with a couple of companies recently, who explicitly
demanded
om is right here.
log_checkpoint and checkpoint_warning are for totally different people.
we might just want to do one thing: we might want to state explicitly
that the database cannot break down if this warning shows up.
many people are scared to death that this warning somehow indicates that
PostgreSQL i
hello ...
did you check out antonin houska's patches?
we basically got code, which can do that.
many thanks,
hans
On 04/02/2017 03:30 PM, Konstantin Knizhnik wrote:
> Hi hackers and personally Robet (you are the best expert in both areas).
> I want to ask one more question
85 matches
Mail list logo
