Bruce Momjian <[EMAIL PROTECTED]> writes:
> I remember the thread but didn't see a TODO in there at the time.
* Make row-wise comparisons work per SQL spec
regards, tom lane
---(end of broadcast)---
TIP 7: don't forget to in
Tatsuo Ishii wrote:
> > > Tatsuo Ishii <[EMAIL PROTECTED]> writes:
> > > > I guess this means that PostgreSQL does not fully support SQL's
> > > > row-wise comparison. We need to add this to the TODO list?
> > >
> > > I thought it was there already ... certainly this has been discussed
> > > befor
On Thursday 09 September 2004 21:30, Bruce Momjian wrote:
> Tom Lane wrote:
> > Andrew Dunstan <[EMAIL PROTECTED]> writes:
> > > ISTM one problem is we are inconsistent about it - \d and \dt don't
> > > show system objects, but \df shows system functions. Reading TFM is a
> > > good thing, but so
Andrew Dunstan wrote:
> >>I think Bruce was mostly trying to make all the similar tests look
> >>alike. Also I agree that "if a && !b" is clearer than "if !b && a";
> >>the latter requires a bit more thought to parse the extent of the !
> >>operator...
> >>
> >>
> >
> >Right, just consistency.
Added to open items list:
* fix permissions on sequences restored via pg_dump
---
Michael Fuhr wrote:
> PostgreSQL version: 8.0.0beta1
> Operating system : Solaris 9
>
> Backups created by pg_dump/pg_dumpall don'
Tom Lane wrote:
> Andrew Dunstan <[EMAIL PROTECTED]> writes:
> > ISTM one problem is we are inconsistent about it - \d and \dt don't
> > show system objects, but \df shows system functions. Reading TFM is a
> > good thing, but so is consistency.
>
> Well, one of the subarguments here is whether
On Fri, Sep 10, 2004 at 02:10:08AM +0200, Gaetano Mendola wrote:
> Greg Stark wrote:
>
> >"Simon Riggs" <[EMAIL PROTECTED]> writes:
> >
> >
> >>I've just been asked to clarify what actually happens when a DELETE takes
> >>place, and what happens to TOASTed data.
> >
> >What does this have to do w
Joe Conway wrote:
James William Pye wrote:
Looking at get_python_lib(), I'm not so sure that I'm correct:
It does seem to work for me:
# python -c "from distutils.sysconfig import get_python_lib as f; import
os; print os.path.join(f(plat_specific=1,standard_lib=1),'config')"
/usr/lib64/python2.3/c
Greg Stark wrote:
"Simon Riggs" <[EMAIL PROTECTED]> writes:
I've just been asked to clarify what actually happens when a DELETE takes
place, and what happens to TOASTed data.
What does this have to do with "x86_64 configure problem"?
I believe this was a new thread but Outlook or the new server
Murat Kantarcioglu wrote:
For our research project, I need to implement an encryption support for
Postgressql. At this current phase, I need to at least support page
level encryption In other words, each page that belongs to a certain
sensitive table will be stored encrypted on the harddisk.
Si
Paul Tillotson <[EMAIL PROTECTED]> writes:
> Given that the client does not write pages to the disk, this would be
> back-end encryption. Just out of curiosity, what threat model does
> this sort of encryption protect against? Surely any attacker who can
> read the files off the disk can also ge
Given that the client does not write pages to the disk, this would be
back-end encryption. Just out of curiosity, what threat model does this
sort of encryption protect against? Surely any attacker who can read
the files off the disk can also get the password used to encrypt them.
Or would t
Murat,
> For our research project, I need to implement an encryption support for
> Postgressql. At this current phase, I need to at least support page
> level Âencryption In other words, each page that belongs to a certain
> sensitive table will be stored encrypted on the harddisk.
Are you planni
> > Tatsuo Ishii <[EMAIL PROTECTED]> writes:
> > > I guess this means that PostgreSQL does not fully support SQL's
> > > row-wise comparison. We need to add this to the TODO list?
> >
> > I thought it was there already ... certainly this has been discussed
> > before ...
>
> This was discussed (i
"Simon Riggs" <[EMAIL PROTECTED]> writes:
>> Tom Lane wrote
>> It would be nice to push the TOAST deletions off to become the
>> responsibility of VACUUM, but I'm not entirely sure how to do that
>> without giving up the UPDATE optimization of shared values.
> That could be optimised, but there ar
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
> While you are it, why not make it
> Informational
> (S = show system objects)
> (+ = show more detail about each object)
> \l[+]list all databases
> \d[S]list tables, views, and sequences
> \d[S][+] NAME
> Tom Lane wrote
> "Simon Riggs" <[EMAIL PROTECTED]> writes:
> > My answer was this, though this was not thought accurate (on the DELETE
> > aspect):
>
> This is correct as far as it goes, but given the question I imagine some
> further detail is appropriate:
>
> * When deleting a row that has out-
"Simon Riggs" <[EMAIL PROTECTED]> writes:
> My answer was this, though this was not thought accurate (on the DELETE
> aspect):
This is correct as far as it goes, but given the question I imagine some
further detail is appropriate:
* When deleting a row that has out-of-line-toasted fields, we must
On Thu, 9 Sep 2004, Alvaro Herrera wrote:
> > In libpq there was some files that was not scanned for translated strings
> > and in scan.l there was a call to gettext() missing which made error
> > messages into a mix of english and swedish (in my case).
>
> I see this problem too. I was about to
"Simon Riggs" <[EMAIL PROTECTED]> writes:
> I've just been asked to clarify what actually happens when a DELETE takes
> place, and what happens to TOASTed data.
What does this have to do with "x86_64 configure problem"?
--
greg
---(end of broadcast)--
On R, 2004-09-10 at 00:03, Murat Kantarcioglu wrote:
> My questions are in order to support page level encryption(i,e encrypt
> each page before writing back to disk and decrypt each page after we
> read from disk.) which parts of the code should be changed?
> Our more simply, is /src/backend/sto
I've just been asked to clarify what actually happens when a DELETE takes
place, and what happens to TOASTed data. The MVCC never-update-in-place
phrase caused some debate over what happens. I couldn't find a specific and
conclusive comment on this that I trust to be completely up to date. One may
For our research project, I need to implement an encryption support for
Postgressql. At this current phase, I need to at least support page
level encryption In other words, each page that belongs to a certain
sensitive table will be stored encrypted on the harddisk.
Since we are trying to have
James William Pye wrote:
Looking at get_python_lib(), I'm not so sure that I'm correct:
It does seem to work for me:
# python -c "from distutils.sysconfig import get_python_lib as f; import
os; print os.path.join(f(plat_specific=1,standard_lib=1),'config')"
/usr/lib64/python2.3/config
Any other p
On Thu, 2004-09-09 at 12:28, James William Pye wrote:
> That should work, regardless of the lib directory that Python is
> installed to.
Looking at get_python_lib(), I'm not so sure that I'm correct:
if os.name == "posix":
libpython = os.path.join(prefix,
I have someone that is asking if you can recover some tablespaces in a
database, but leave the others online ... apparently its a feature of
tablespaces under Oracle ... I could see it for schemas, but sounds like
it could cause problems depeending on how you are using tablespaces ...
Mar
On Thu, 2004-09-09 at 11:17, Joe Conway wrote:
> On an x86_64 machine I'm finding that I cannot configure --with-python
> without the attached patch. Undoubtedly there is a better way to fix
> this -- any suggestions?
python_configdir=`${PYTHON} -c "from distutils.sysconfig import
get_python_lib
On an x86_64 machine I'm finding that I cannot configure --with-python
without the attached patch. Undoubtedly there is a better way to fix
this -- any suggestions?
Another configure issue: I find that --enable-depend breaks parallel builds:
make -j 2
[...]
make[3]: Entering directory
`/opt/s
I wanted to know the contents of the buffer cache in 7.4, so I created
this function and view that seems to work ok:
/* Takes relfilenode (from pg_class) and returns the number of
* buffer cache pages it is using.
*/
PG_FUNCTION_INFO_V1(block_count);
Datum
block_count(PG_FUNCTION_ARGS)
{
"Greg Sabino Mullane" <[EMAIL PROTECTED]> writes:
> To clarify the 'S' a bit more, here is the output from \? in my new patch:
This looks nice perhaps do it for "+" as well?
> Informational:
> Modifiers
> S Show system objects
> + Additional detail
> \l[+] list all
Tom Lane schrieb:
Andrew Dunstan <[EMAIL PROTECTED]> writes:
I'm not sure exactly what Bruce checked, so I just spent a few cycles
making sure that we did not inadvertantly pick up a define of WIN32 from
windows.h anywhere else. I *think* we are OK on that. However, ISTM this
is a foot just wait
> Tatsuo Ishii <[EMAIL PROTECTED]> writes:
> > I guess this means that PostgreSQL does not fully support SQL's
> > row-wise comparison. We need to add this to the TODO list?
>
> I thought it was there already ... certainly this has been discussed
> before ...
This was discussed (including a possi
On Thu, Sep 09, 2004 at 11:37:13AM -, Greg Sabino Mullane wrote:
> To clarify the 'S' a bit more, here is the output from \? in my new patch:
>
> Informational (S = show system objects)
> \llist all databases (add "+" for more detail)
> \d[S] list tables, view
On Thu, Sep 09, 2004 at 09:09:31AM +0200, Dennis Bjorklund wrote:
> I've been going over the translation again and found 2 places that was
> broken.
>
> In libpq there was some files that was not scanned for translated strings
> and in scan.l there was a call to gettext() missing which made error
Andrew Dunstan <[EMAIL PROTECTED]> writes:
> ISTM one problem is we are inconsistent about it - \d and \dt don't
> show system objects, but \df shows system functions. Reading TFM is a
> good thing, but so is consistency.
Well, one of the subarguments here is whether we are going to change the
Tom Lane wrote:
Bruce Momjian <[EMAIL PROTECTED]> writes:
Tom Lane wrote:
I thought the "S" suggestion was much better than this.
My problem is that it uses a letter as a modifier, while all other
letters are object specifications. '+' is a modifier. We need another
modifier th
Andrew Dunstan <[EMAIL PROTECTED]> writes:
> I'm not sure exactly what Bruce checked, so I just spent a few cycles
> making sure that we did not inadvertantly pick up a define of WIN32 from
> windows.h anywhere else. I *think* we are OK on that. However, ISTM this
> is a foot just waiting to be
Bruce Momjian wrote:
Tom Lane wrote:
"Andrew Dunstan" <[EMAIL PROTECTED]> writes:
I don't understand most of this patch. What difference does changing the
preprocessor test order make?
I think Bruce was mostly trying to make all the similar tests look
alike. Also I agree that "if a
Bruce Momjian <[EMAIL PROTECTED]> writes:
> Tom Lane wrote:
>> I thought the "S" suggestion was much better than this.
> My problem is that it uses a letter as a modifier, while all other
> letters are object specifications. '+' is a modifier. We need another
> modifier that isn't a letter. No
OK thanks !
Le Jeudi 9 Septembre 2004 18:14, Thomas F.O'Connell a écrit :
> pg_autovacuum will still be in contrib as of 8.0. It did not make
> integration with the core distribution.
>
> -tfo
>
> On Sep 9, 2004, at 11:09 AM, Hervé Piedvache wrote:
> > Hi,
> >
> > I was thinking that new things wi
Tatsuo Ishii <[EMAIL PROTECTED]> writes:
> I guess this means that PostgreSQL does not fully support SQL's
> row-wise comparison. We need to add this to the TODO list?
I thought it was there already ... certainly this has been discussed
before ...
regards, tom lane
--
Tom Lane wrote:
> Bruce Momjian <[EMAIL PROTECTED]> writes:
> > I talked to Greg via chat and it looks like '&' is the best choice for
> > adding system object display:
>
> > \d& shows system stuff
>
> Yech, that's awful. It looks ugly and it commandeers a punctuation
> symbol that we might
pg_autovacuum will still be in contrib as of 8.0. It did not make
integration with the core distribution.
-tfo
On Sep 9, 2004, at 11:09 AM, Hervé Piedvache wrote:
Hi,
I was thinking that new things will appear in v8.0 about pg_autovacuum
??
But I find nothing new in README and/or Version Histor
Hi,
I was thinking that new things will appear in v8.0 about pg_autovacuum ??
But I find nothing new in README and/or Version History
Any help ?
Regards,
--
Hervé Piedvache
Elma Ingénierie Informatique
6 rue du Faubourg Saint-Honoré
F-75008 - Paris - France
Pho. 33-144949901
Fax. 33-1449
Bruce Momjian <[EMAIL PROTECTED]> writes:
> I talked to Greg via chat and it looks like '&' is the best choice for
> adding system object display:
> \d& shows system stuff
Yech, that's awful. It looks ugly and it commandeers a punctuation
symbol that we might wish to use for something else
I talked to Greg via chat and it looks like '&' is the best choice for
adding system object display:
\d& shows system stuff
\df& shows system functions
etc.
Greg is going to work on a patch for 8.1.
Following result seems strange since it is not what the standard
expects:
test=# select (1,1) > (0,10);
?column?
--
f
(1 row)
On the other hand I see following in the doc:
-
9.17.5. Row-wise Comparison
(expression [, expression ...]) operator (
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
> Agreed it would be nice to more clearly distingush user functions from
> system ones, but how? I can't see how 'S' is going to help us because
> \dS already shows system tables. Would it be \dfS? What is the logic
> to that? Having 'S' be a f
Greg Sabino Mullane wrote:
[ There is text before PGP section. ]
>
[ PGP not available, raw data follows ]
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
>
> Greg Stark wrote:
> > Well there's always \dtS and \dvS I don't see why typing \dfS is any harder.
> >
> > It would be nice for thi
I've been going over the translation again and found 2 places that was
broken.
In libpq there was some files that was not scanned for translated strings
and in scan.l there was a call to gettext() missing which made error
messages into a mix of english and swedish (in my case).
Normally I just c
50 matches
Mail list logo
